{"id":"CVE-2026-18214","aliases":["BIT-keycloak-2026-18214","EUVD-2026-51485","GHSA-wmhp-w67v-6jm5"],"status":"published","title":"Keycloak-services: keycloak-services: google external access-token exchange bypasses hosted-domain restriction","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.","severity":{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00402,"percentile":0.3494,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-862"],"published":"2026-07-31T07:08:26Z","modified":"2026-09-17T14:45:07Z","fixes":[{"ecosystem":"Bitnami","package":"keycloak","fixed_in":["26.7.3"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Bitnami","package":"keycloak","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"26.7.3"}]}]}],"products":[{"vendor":"red hat","product":"red hat build of keycloak 26.6"},{"vendor":"red hat","product":"red hat build of keycloak 26.6.7"},{"vendor":"red hat","product":"red hat data grid 8"},{"vendor":"red hat","product":"red hat jboss enterprise application platform expansion pack"},{"vendor":"red hat","product":"red hat single sign-on 7"},{"vendor":"redhat","product":"build_of_keycloak"}],"references":[{"url":"https://access.redhat.com/errata/RHSA-2026:68277","tags":["vendor-advisory","x_refsource_REDHAT","web"]},{"url":"https://access.redhat.com/errata/RHSA-2026:68278","tags":["vendor-advisory","x_refsource_REDHAT","web"]},{"url":"https://access.redhat.com/security/cve/CVE-2026-18214","tags":["vdb-entry","x_refsource_REDHAT","Vendor Advisory","advisory"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2508308","tags":["issue-tracking","x_refsource_REDHAT","Issue Tracking","Vendor Advisory","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-18214","tags":["web"]},{"url":"https://github.com/advisories/GHSA-wmhp-w67v-6jm5"}],"sources":{"cve":[{"id":"CVE-2026-18214","title":"Keycloak-services: keycloak-services: google external access-token exchange bypasses hosted-domain restriction","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.","status":"published","published":"2026-07-31T07:08:26.652Z","modified":"2026-09-16T18:34:27.553Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-862"],"updated_at":"2026-11-02T14:20:12.260247Z"}],"euvd":[{"id":"EUVD-2026-51485","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.","status":"published","published":"2026-07-31T07:08:26Z","modified":"2026-09-16T18:34:27Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"medium"}],"updated_at":"2026-11-02T17:28:14.682482Z"}],"ghsa":[{"id":"GHSA-wmhp-w67v-6jm5","title":"Keycloak allows users to log in using Google accounts and can be configured to only allow users...","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.","status":"published","published":"2026-07-31T09:31:18Z","modified":"2026-09-16T18:32:20Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"medium"}],"cwes":["CWE-862"],"updated_at":"2026-11-02T15:12:01.408765Z"}],"nvd":[{"id":"CVE-2026-18214","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.","status":"published","published":"2026-07-31T08:16:27.753Z","modified":"2026-09-16T19:17:09.047Z","cvss":[{"version":"3.1","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"medium","assessor":"secondary"},{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","level":"high","assessor":"primary"}],"cwes":["CWE-862"],"updated_at":"2026-11-02T14:12:34.290716Z"}],"osv":[{"id":"BIT-keycloak-2026-18214","title":"Keycloak-services: keycloak-services: google external access-token exchange bypasses hosted-domain restriction","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.","status":"published","published":"2026-08-31T14:37:14.664Z","modified":"2026-09-17T14:45:07.864294949Z","updated_at":"2026-11-02T15:28:32.162822Z"}]}}