# CVE-2026-96447: Keycloak TokenManager identity rebinding in stateless token validation

Source: https://junglewise.ai/threats/cve-2026-96447-a-flaw-was-found-in-the-tokenmanager-component-of-keycloak-an  
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-96447 · Severity: medium · CVSS 4.2 · Published 2026-11-06

Keycloak is an open-source identity and access management platform used to control who can access applications and resources. This flaw allows an attacker holding an old access token to impersonate a new service account if a deleted client is recreated with the same ID, potentially gaining unauthorized access to applications and data. Exploitation requires specific conditions: an administrator must delete and recreate a client while an attacker possesses a valid token from the original client.

Technologies: [Keycloak](https://junglewise.ai/threats/technologies/keycloak). Vendors: [Keycloak](https://junglewise.ai/threats/vendors/keycloak).

## Quick answers

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

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

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

**Is there a fix for CVE-2026-96447?** 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-96447 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-96447?** Check whether you run 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 TokenManager component in Keycloak improperly validates stateless access tokens when the original user ID no longer exists, falling back to username-based user resolution without verifying the token subject binding. An attacker with a valid stateless token from a deleted client can exploit this during client recreation to gain the identity and permissions of the replacement service account. This is a CWE-287 improper authentication vulnerability requiring network access and low privileges (a valid existing token).

## Affected products

- Keycloak 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-96447](https://access.redhat.com/security/cve/CVE-2026-96447)

## Related threats

- [Keycloak login-failure storage synchronization error in MySQL/MariaDB](https://junglewise.ai/threats/cve-2026-112201-a-flaw-was-found-in-the-login-failure-storage-component-of)
- [Keycloak PKCE bypass in login after password reset](https://junglewise.ai/threats/cve-2026-125652-a-flaw-was-found-in-the-keycloak-services-component-of-keycloak)
- [Keycloak server arbitrary code execution in client authorization](https://junglewise.ai/threats/cve-2026-120984-a-flaw-was-found-in-the-keycloak-server-s-client-management)
- [Keycloak token sanitization bypass in protocol mapper](https://junglewise.ai/threats/cve-2026-97848-a-flaw-was-found-in-the-token-sanitization-logic-of-keycloak-an)
- [Keycloak Dynamic Client Registration privilege escalation](https://junglewise.ai/threats/cve-2026-96547-a-flaw-was-found-in-the-dynamic-client-registration-component-of)