Skip to main content

Red Hat Keycloak EUVDEUVD-2026-51485

| CVE-2026-18214 HIGH
Missing Authorization (CWE-862)
2026-07-31 redhat GHSA-wmhp-w67v-6jm5
8.1
CVSS 3.1 · NVD
Share

Severity by source

Vendor (redhat) PRIMARY
MEDIUM
qualitative
NVD
8.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
vuln.today AI
8.1 HIGH

AV:N because the token exchange endpoint is network-accessible; PR:L because any Google account (freely obtainable) is required; C:H/I:H for full realm access; A:N as availability is unaffected.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Red Hat
6.8 MEDIUM
qualitative

Primary rating from Vendor (redhat).

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

Lifecycle Timeline

6
Analysis Updated
Aug 07, 2026 - 18:32 vuln.today
v2 (cvss_changed)
Re-analysis Queued
Aug 07, 2026 - 18:22 vuln.today
cvss_changed
Severity Changed
Aug 07, 2026 - 18:22 NVD
MEDIUM HIGH
CVSS changed
Aug 07, 2026 - 18:22 NVD
6.8 (MEDIUM) 8.1 (HIGH)
Analysis Generated
Jul 31, 2026 - 07:52 vuln.today
CVE Published
Jul 31, 2026 - 07:08 cve.org
MEDIUM 6.8

DescriptionNVD

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.

AnalysisAI

Token exchange in Keycloak bypasses Google Workspace domain allowlist restrictions, enabling any valid Google account holder - regardless of their domain - to swap a Google OAuth token for a Keycloak realm token and gain unauthorized access. Affected deployments are those specifically configured to restrict Google-based logins to approved Workspace domains while also having token exchange enabled; both conditions must be present. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Obtain free Google account
Delivery
Authenticate to Google, acquire OAuth token
Exploit
Submit Google token to Keycloak token exchange endpoint
Execution
Domain allowlist check skipped (CWE-862)
Persist
Keycloak issues valid realm session token
Impact
Access integrated applications as unauthorized user

Vulnerability AssessmentAI

Exploitation Exploitation requires three simultaneous conditions: (1) the Keycloak realm must have Google configured as an identity provider with a specific Google Workspace domain allowlist in place (e.g., restricting logins to @targetcorp.com); (2) the Keycloak token exchange feature must be explicitly enabled for the realm - this is an opt-in configuration, not a default; and (3) the attacker must possess any valid Google account, regardless of domain. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The CVSS base score of 8.1 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N) accurately reflects the network-reachable, low-complexity nature of the flaw with significant confidentiality and integrity impact. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker who holds any freely-created Google account (e.g., attacker@gmail.com) authenticates to Google and obtains a valid Google OAuth access or ID token. They then send that token directly to the Keycloak token exchange endpoint for the targeted realm, which processes it without applying the configured Workspace domain allowlist check. …
Remediation Consult the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-18214 for an updated patch; no exact fixed version number is confirmed in available data at time of analysis. … Detailed patch versions, workarounds, and compensating controls in full report.

Recommended ActionAI

Within 24 hours, conduct a configuration audit of all Keycloak instances to identify which have both Google Workspace domain allowlist active AND token exchange enabled-only systems meeting both criteria are at risk. …

Sign in for detailed remediation steps and compensating controls.

Threat intelligence, references, and detailed analysis are available after sign-in.

CVE-2026-16442 CRITICAL
9.8 Aug 05

Account takeover in Keycloak (Red Hat build of Keycloak, Red Hat Single Sign-On 7) arises because the IdP-initiated SAML

CVE-2026-18963 CRITICAL
9.1 Aug 18

Account takeover in Red Hat Build of Keycloak allows an unauthenticated attacker to abuse the reset-credentials flow in

CVE-2026-16443 CRITICAL
9.1 Aug 05

Authentication bypass in Red Hat Build of Keycloak (and Red Hat Single Sign-On 7) lets an unauthenticated attacker forge

CVE-2026-15572 HIGH
8.8 Aug 05

Privilege escalation in Red Hat Build of Keycloak's Dynamic Client Registration (DCR) grants an attacker with low-privil

CVE-2026-9800 HIGH
8.1 Jun 25

Authorization bypass in the Keycloak Policy Enforcer allows any authenticated user to circumvent all enforced access con

CVE-2026-15573 HIGH
8.1 Aug 05

URI normalization bypass in Keycloak's Authorization Services PathMatcher allows authenticated low-privilege users to re

CVE-2026-16102 HIGH
8.1 Aug 05

Privilege escalation in Keycloak's Dynamic Client Registration (DCR) component allows attackers with standard user accou

CVE-2026-11800 HIGH
8.1 Jun 25

Signature-verification bypass in Keycloak (and Red Hat's Keycloak-based products such as Red Hat Single Sign-On 7 and Re

CVE-2026-18215 HIGH
8.1 Jul 31

Tenant-restriction bypass in Keycloak's Microsoft identity provider integration allows attackers holding any valid Micro

CVE-2026-18967 HIGH
8.1 Aug 06

Session hijacking via SAML assertion replay in Keycloak's SAML broker component allows adjacent-network attackers to aut

CVE-2026-7504 HIGH
8.1 May 19

Open redirect in Red Hat build of Keycloak permits remote attackers to send victims to attacker-controlled hosts by abus

CVE-2026-9087 HIGH
8.1 May 20

Identity linking bypass in Red Hat build of Keycloak allows an attacker controlling a second account on the same upstrea

Vendor StatusVendor

Share

EUVD-2026-51485 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy