Description
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.
Affected products
redhat: build of keycloak
References4
- access.redhat.com/security/cve/CVE-2026-18214 Vendor Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2508308 Issue TrackingVendor Advisory
- access.redhat.com/errata/RHSA-2026:68277
- access.redhat.com/errata/RHSA-2026:68278
Metrics
- CVSS 3.1
-
8.1
HIGH
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N - EPSS — exploit probability
- 0% percentile: 35 · as of 13 November 2026
- CWE
- CWE-862
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.