Bug 2577140 (CVE-2026-133224)

Summary: CVE-2026-133224 org.keycloak:keycloak-services: Pre-revocation ID tokens can mint fresh UMA RPTs after realm not-before
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: unspecifiedCC: aschwart, aszczucz, boliveir, drichtar, mposolda, pjindal, rmartinc, ssilvert, sthorger, vmuzikar
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in Keycloak. When an administrator revokes tokens by setting a not-before revocation cutoff, Keycloak fails to enforce this boundary when processing User-Managed Access (UMA) grant requests using ID token claims. An authenticated remote user with an active session can submit a previously revoked ID token to receive a fresh Requesting Party Token (RPT). This flaw allows an attacker to bypass token revocation and retain unauthorized access to protected resources.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-11-19 17:57:50 UTC
When an administrator revokes existing tokens by raising the realm (or

client/user) not-before value, ID tokens issued before that cutoff are
still accepted by the UMA grant when they are submitted as a claim
token in the ID token format. Keycloak verifies the signature, client
and expiration of the ID token but does not enforce the not-before
revocation boundary. As long as the user's session is still active,
Keycloak builds a new identity from it and issues a fresh Requesting
Party Token (RPT) carrying the evaluated authorization permissions.
This defeats the administrator's explicit token revocation. The
affected endpoint is the token endpoint (POST
/realms/{realm}/protocol/openid-connect/token) using the UMA grant
(urn:ietf:params:oauth:grant-type:uma-ticket) with claim_token_format
set to the ID token format.