Description
A flaw was found in the TokenManager component of Keycloak, an open-source identity and access management solution. The issue occurs during the validation of stateless access tokens when the original user ID no longer exists. Keycloak incorrectly falls back to using the username to identify the user without verifying if the identity matches the original token subject. This could allow an attacker with an old token to gain access to a newly created service account if it shares the same client ID as a previously deleted one.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Red Hat | Red Hat build of Keycloak 26.6 | — | — |
| Red Hat | Red Hat build of Keycloak 26.6.8 | — | — |
| Red Hat | Red Hat Single Sign-On 7 | — | — |
Advisories 1
- WID-SEC-2026-4375 Keycloak: Mehrere Schwachstellen BSI CERT-Bund (WID) · Nov 11, 2026
References
- RHSA-2026:95761 vendor-advisory
- RHSA-2026:95762 vendor-advisory
- https://access.redhat.com/security/cve/CVE-2026-96447 vdb-entry
- RHBZ#2539288 issue-tracking