Bug 2577140 (CVE-2026-133224) - CVE-2026-133224 org.keycloak:keycloak-services: Pre-revocation ID tokens can mint fresh UMA RPTs after realm not-before
Summary: CVE-2026-133224 org.keycloak:keycloak-services: Pre-revocation ID tokens can ...
Keywords:
Status: NEW
Alias: CVE-2026-133224
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-11-19 17:57 UTC by OSIDB Bzimport
Modified: 2026-11-19 18:27 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

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.


Note You need to log in before you can comment on or make changes to this bug.