Skip to main content
VulnerabilityPublished

CVE-2026-133224: Red Hat Build of Keycloak · Use of a Key Past its Expiration Date

Affects Red Hat Build of KeycloakSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium.

Data as of 20 Nov 2026, 01:51 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 advises explicitly terminating active user sessions when revoking tokens rather than relying solely on the not-before timestamp cutoff. Alternatively, disable User-Managed Access (UMA) authorization on clients that do not require fine-grained authorization. These configuration changes take effect immediately without requiring a Keycloak service restart. Terminating sessions will force users to re-authenticate, and disabling UMA will stop issuance of Requesting Party Tokens for the client.

Description

A vulnerability in Red Hat Build of Keycloak allows an authenticated user with an active session to bypass token revocation when User-Managed Access (UMA) authorization is enabled. Specifically, Keycloak fails to enforce the not-before revocation cutoff for UMA grant requests using ID token claims, enabling reuse of previously revoked ID tokens to obtain fresh Requesting Party Tokens (RPTs). This issue affects environments configured with UMA and requires an existing authenticated session.

References

Community reviews

Loading reviews…