# CVE-2026-96460: Keycloak token exchange lifetime bypass in Standard Token Exchange V2

Source: https://junglewise.ai/threats/cve-2026-96460-a-flaw-was-found-in-the-token-exchange-mechanism-of-keycloak-when  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-06. Updated: 2026-11-06  
License: CC BY 4.0 with a link back

CVE-2026-96460 · Severity: medium · CVSS 5.4 · Published 2026-11-06

Keycloak is an identity and access management system that handles authentication and token-based authorization for enterprise applications. A flaw in its token exchange feature allows an authenticated attacker to indefinitely renew access tokens by repeatedly exchanging them, enabling persistent access even after an administrator disables the original client. This could lead to unauthorized continued access to protected resources and services.

Technologies: [Red Hat Keycloak](https://junglewise.ai/threats/technologies/red-hat-keycloak). Vendors: [Red Hat](https://junglewise.ai/threats/vendors/red-hat).

## Quick answers

**Is CVE-2026-96460 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-96460 being exploited in the wild.

**How severe is CVE-2026-96460?** Medium severity, with a CVSS score of 5.4, published 6 November 2026.

**Which products and versions are affected?** Red Hat Keycloak.

**Is there a fix for CVE-2026-96460?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-96460 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-96460?** Check whether you run Red Hat Keycloak. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability exists in Standard Token Exchange V2, where the system issues new tokens with a fresh lifetime based on the requester client's configuration instead of respecting the original token's expiration time. An authenticated requester with valid service-account tokens can exploit this by repeatedly exchanging tokens to maintain access indefinitely, bypassing administrative revocation. The root cause is incorrect implementation of token lifetime binding (CWE-303: Access Control).

## Affected products

- Red Hat Keycloak

## Timeline

- 2026-11-06: disclosed

## References

- [https://access.redhat.com/downloads/content/package-browser/](https://access.redhat.com/downloads/content/package-browser/)
- [https://access.redhat.com/security/cve/CVE-2026-96460](https://access.redhat.com/security/cve/CVE-2026-96460)

## Related threats

- [Red Hat Keycloak missing authorization check in group reparenting](https://junglewise.ai/threats/cve-2026-116468-a-flaw-was-found-in-the-group-move-and-organization-group)
- [Keycloak privilege escalation via client authentication manipulation](https://junglewise.ai/threats/cve-2026-9797-a-flaw-was-found-in-keycloak-s-administrative-services-org)
- [Keycloak Account REST API session manipulation](https://junglewise.ai/threats/cve-2026-97367-a-flaw-was-found-in-the-keycloak-account-rest-api-where-it)
- [Keycloak SAML broker ProxyRestriction bypass](https://junglewise.ai/threats/cve-2026-92856-a-flaw-was-found-in-the-saml-brokering-component-of-keycloak-an)
- [Keycloak authorization bypass in Dynamic Client Registration](https://junglewise.ai/threats/cve-2026-109081-a-flaw-was-found-in-keycloak-the-dynamic-client-registration-dcr)