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.
Advisories

No advisories yet.

Fixes

Solution

No solution given by the vendor.


Workaround

Explicitly terminate active user sessions when revoking tokens, or disable User-Managed Access (UMA) authorization on clients where fine-grained authorization is not needed. To reduce exposure: - In the Keycloak Administration Console, navigate to the target realm, select 'Sessions', and explicitly terminate active sessions for the relevant user or realm rather than relying solely on the not-before timestamp cutoff. - For OpenID Connect clients that do not require fine-grained resource permissions, ensure that 'Authorization Enabled' is set to 'OFF' in the client settings. Caveats: Terminating active user sessions will immediately disconnect active sessions and require users to re-authenticate. Disabling authorization services on a client disables the issuance of Requesting Party Tokens (RPTs) for that client. These configuration changes take effect immediately and do not require restarting the Keycloak service.

History

Fri, 20 Nov 2026 01:45:00 +0000

Type Values Removed Values Added
Title org.keycloak:keycloak-services: Pre-revocation ID tokens can mint fresh UMA RPTs after realm not-before Org.keycloak:keycloak-services: pre-revocation id tokens can mint fresh uma rpts after realm not-before
First Time appeared Redhat
Redhat build Keycloak
Redhat red Hat Single Sign On
CPEs cpe:/a:redhat:build_keycloak:
cpe:/a:redhat:red_hat_single_sign_on:7
Vendors & Products Redhat
Redhat build Keycloak
Redhat red Hat Single Sign On
References

Fri, 20 Nov 2026 00:15:00 +0000

Type Values Removed Values Added
Description 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.
Title org.keycloak:keycloak-services: Pre-revocation ID tokens can mint fresh UMA RPTs after realm not-before
Weaknesses CWE-324
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}

threat_severity

Moderate


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published:

Updated: 2026-11-20T01:41:25.120Z

Reserved: 2026-11-19T15:33:27.469Z

Link: CVE-2026-133224

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-11-19T17:56:51Z

Links: CVE-2026-133224 - Bugzilla

cve-icon OpenCVE Enrichment

No data.

Weaknesses