keycloak-services is vulnerable to Authentication Bypass
42
CVE Score
Medium
Authentication Bypass
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.
Upgrade org.keycloak:keycloak-services to the patched version. The fix requires the token subject to match a regenerated pairwise subject before accepting a username fallback.
You are affected if you use a vulnerable version of org.keycloak:keycloak-services and a stateless token outlives deletion of its original user or service account and a new account reuses the preferred username.
12.0.0 - 26.8.1
Fixed in 26.8.2keycloak-services is vulnerable to Authentication Bypass in versions 12.0.0 - 26.8.1.
Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.
No credit card required | Scan results in 32 seconds.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.