Keycloak Token Exchange Bypass: Domain Restriction Lapse
CVE-2026-18214 Published on July 31, 2026
Keycloak-services: keycloak-services: google external access-token exchange bypasses hosted-domain restriction
Keycloak allows users to log in using Google accounts and can be configured to only allow users from specific Google Workspace domains. A flaw was found where the token exchange feature, which allows swapping a Google token for a Keycloak token, does not check these domain restrictions. This means an attacker with a valid Google account from a different domain could bypass the security check and gain access to the Keycloak realm.
Vulnerability Analysis
CVE-2026-18214 is exploitable with network access, and requires small amount of user privileges. This vulnerability is consided to have a high level of attack complexity. The potential impact of an exploit of this vulnerability is considered to have a high impact on confidentiality and integrity, and no impact on availability.
Timeline
Reported to Red Hat.
Made public.
Weakness Type
What is an AuthZ Vulnerability?
The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
CVE-2026-18214 has been classified to as an AuthZ vulnerability or weakness.
Products Associated with CVE-2026-18214
Want to know whenever a new CVE is published for Red Hat products? stack.watch will email you.
