CVE-2026-96447

Read full 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.

CVSS 4.2 (MEDIUM)

Attention and evidence

HYPE SCORE

0.0/10

REALITY · THREAT PRIORITY

1.5–4.0/10

Missing inputs: range of priority

Evidence confidence: Insufficient evidence

Why this priority?

Technical severity: CVSS 4.2: +1.47

Fresh prediction unavailable

General review priority, not probability, victim count or asset-specific risk. A range covers missing CVSS/EPSS inputs within the current evidence state.

Sources: 1 documents and public datasets.

Hype components

Headline sample (25%)

0/100

Press, 30 days (60%)

0/100

Grounded branding (15%)

0/100

HYPE TOTAL0/100

Sources and documents

Latest Vulnerabilities

Technical advisory · 06 Nov 2026, 06:16 · CVE-2026-96447 - Keycloak-services: keycloak-services: stateless token preferred_username fallback enables identity rebinding

Score evolution

● Hype ● Reality

First record: hype 0.0 · reality 1.5 (2026-11-06 07:25). The curve appears once the score changes.

Public exploit evidence

Public exploit entries / repo candidates

Evidence context and dated references

Reality is general threat/review priority, combining observed exploitation, CVSS severity and fresh EPSS. Evidence confidence is separate. This is not calibrated risk, a victim count or an asset-specific assessment. A range reflects missing numeric inputs. Published 0 days ago. Exploitation evidence usually takes weeks to show up: a low reality score can mean there is no data yet, not that the flaw is mild.

Evidence in context

Confidence in exploitation evidence: Insufficient evidence
Priority basis: Exploitation in attacks unconfirmed; CVSS 4.2; fresh prediction unavailable
Attention, last 30 days: 0 distinct story titles; 0 press documents; 0 publisher domains.
Technical potential: network access, low privileges, no user interaction, additional attack conditions.
Observed activity: No exploitation observation is recorded.
Known scale: Not quantified.
Evidence confidence basis: Insufficient evidence

Score evaluated: 2026-11-06 07:25:57.352507+00:00 · EPSS snapshot: not available

Source event timeline

Published

06 Nov 2026, 06:02

Score calculated

06 Nov 2026, 07:25