Intel

AIKIDO-2026-111216

keycloak-services is vulnerable to Authentication Bypass

CVE-2026-96447Published 4 days ago
November 16, 2026

42

CVE Score

Medium

Authentication Bypass

Are you affected? Scan for Free

TL;DR

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.

How do I fix this?

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.

Who does this affect?

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.

Versions

12.0.0 - 26.8.1

Fixed in 26.8.2

Background info

keycloak-services is vulnerable to Authentication Bypass in versions 12.0.0 - 26.8.1.

Get secure today,
quickly and for free.

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.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea