Keycloak · CWE-324
Source GCVE Database
Not known to be exploited · CVSS 5.4 Medium.
Data as of 20 Nov 2026, 04:36 UTC
Thin evidence
One scorer or none| CNA (redhat) | CVSS 3.1 | 5.4 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Build of Keycloakkeycloak-services | Affected– | Fixed in– |
| Red Hat Build of Keycloakrhbk/keycloak-rhel9 | Affected– | Fixed in– |
| Red Hat Single Sign-On 7keycloak-services | Affected– | Fixed in– |
| Red Hat Single Sign-On 7rh-sso7-keycloak | Affected– | Fixed in– |
AI-suggested
Red Hat recommends explicitly terminating active user sessions when revoking tokens rather than relying solely on the not-before timestamp cutoff. Administrators should navigate to the Keycloak Administration Console, select the relevant realm and user sessions, and terminate them to enforce revocation. Additionally, for OpenID Connect clients that do not require fine-grained authorization, disable User-Managed Access (UMA) by setting 'Authorization Enabled' to 'OFF' in client settings. These configuration changes take effect immediately and do not require restarting Keycloak. Terminating sessions will disconnect users and require re-authentication, and disabling UMA will prevent issuance of Requesting Party Tokens for those clients.
Description
A vulnerability in Keycloak allows an authenticated user to bypass token revocation when User-Managed Access (UMA) authorization is enabled. Specifically, Keycloak does not enforce the not-before revocation cutoff for UMA grant requests using ID token claims, enabling reuse of revoked ID tokens to mint fresh Requesting Party Tokens (RPTs). This flaw permits unauthorized access continuation but does not allow privilege escalation beyond the active session's permissions.