CVE-2026-96447
CVE-2026-96447
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.
Vulnerability class: Broken Authentication
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.2 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N.
EPSS exploit prediction
No EPSS score from FIRST.org yet. New CVEs usually get one within a few days; no score means no signal yet, not low risk. How EPSS works.
Weakness classification (CWE)
References
- RHSA-2026:95761 (vendor-advisory)
- RHSA-2026:95762 (vendor-advisory)
- access.redhat.com/security/cve/CVE-2026-96447 (vdb-entry)
- RHBZ#2539288 (issue-tracking)
Frequently asked questions
- What is CVE-2026-96447?
- CVE-2026-96447 is a medium-severity vulnerability, classified under Improper Authentication. CVSS score: 4.2/10. Published 2026-11-06.
- How severe is CVE-2026-96447?
- Medium severity. CVSS v3 base score is 4.2 out of 10.