Skip to main content
CVE-2026-133224VulnerabilityPublished

Keycloak · CWE-324

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-133224· Medium 5.4

Not known to be exploited · CVSS 5.4 Medium.

Data as of 20 Nov 2026, 04:36 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.15.4
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Red Hat Build of Keycloakkeycloak-servicesAffected–Fixed in–
Red Hat Build of Keycloakrhbk/keycloak-rhel9Affected–Fixed in–
Red Hat Single Sign-On 7keycloak-servicesAffected–Fixed in–
Red Hat Single Sign-On 7rh-sso7-keycloakAffected–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.

References

Community reviews

Loading reviews…