cve.bz

CVE-2026-96447 Keycloak-services: keycloak-services: stateless token preferred_username fallback enables identity rebinding

4.2 mediumEPSS 0.2%Fix available

Medium (4.2) in red hat. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

4.2 medium
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
redhat (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • Red Hat Red Hat build of Keycloak 26.6: fixed in 26.6.8-2
  • Red Hat Red Hat build of Keycloak 26.6: fixed in 26.6-24

Ask an AI about this CVE

Show the promptExplain CVE-2026-96447 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-96447?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-96447?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-96447 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • 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

Versions

From the CNA's record in the CVE List.

Fixed in

ProductFixed in
Red Hat build of Keycloak 26.626.6.8-2
Red Hat build of Keycloak 26.626.6-24

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

The Red Hat Product Security team has assessed the severity of this vulnerability as Moderate, given that exploitation requires an administrator to delete and recreate a client with the same ID while an attacker holds a valid stateless token from the original client. Successful exploitation allows an attacker to gain the identity and permissions of the replacement service account. The vulnerability's root cause is an improper fallback to username-based resolution in stateless token validation without verifying the binding to the original token subject.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat build of Keycloak 26.6rhbk/keycloak-operator-bundle:26.6.8-2Fixed 2026-11-06RHSA-2026:95762
Red Hat build of Keycloak 26.6rhbk/keycloak-rhel9:26.6-24Fixed 2026-11-06RHSA-2026:95762
Red Hat build of Keycloak 26.6rhbk/keycloak-rhel9-operator:26.6-24Fixed 2026-11-06RHSA-2026:95762
Red Hat build of Keycloak 26.6.8keycloak-servicesFixed 2026-11-06RHSA-2026:95761
Red Hat build of Keycloak 26.6.8rhbk/keycloak-rhel9Fixed 2026-11-06RHSA-2026:95761
Red Hat Single Sign-On 7keycloak-servicesNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-96447.

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON