Service-account impersonation via stateless-token username fallback
Published Nov 6, 2026 · Updated Nov 6, 2026
Authentication bypass in Red Hat build of Keycloak allows remote authenticated users to access a service account via an old token. When the original user ID is absent, TokenManager resolves the stateless token's preferred_username without checking that the resulting identity matches its original subject. Exploitation requires an old token and a recreated service account sharing the deleted client's ID, granting access as the replacement account.
Summary
What happened
Authentication bypass in Red Hat build of Keycloak allows remote authenticated users to access a service account via an old token. When the original user ID is absent, TokenManager resolves the stateless token's preferred_username without checking that the resulting identity matches its original subject. Exploitation requires an old token and a recreated service account sharing the deleted client's ID, granting access as the replacement account.
The record
- CVE
- CVE-2026-96447
- Published
- Nov 6, 2026
- Updated
- Nov 6, 2026
- Vendor
- John Horne
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-287, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 6, 2026CVE publishedPublication date reported by the CVE source.
- Nov 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us