CVE-2026-133224
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.
Statement
This vulnerability is rated as Moderate severity for Red Hat build of Keycloak and Red Hat Single Sign-On because exploitation requires an existing authenticated session and specifically targets environments configured with User-Managed Access (UMA) authorization services. Under default configurations, clients do not have fine-grained authorization services enabled, limiting the attack surface to deployments actively leveraging UMA grant exchange. While an attacker possessing a previously issued identity token can bypass not-before timestamp invalidation to mint new authorization tokens, they cannot elevate privileges beyond what the active user session and role mappings permit.
Mitigation
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.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 5.4 | N/A | N/A |
| Attack Vector | Network | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | Low | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | Low | N/A | N/A |
| Integrity Impact | Low | N/A | N/A |
| Availability Impact | None | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Understanding the Weakness (CWE)
Access Control
Technical Impact: Bypass Protection Mechanism; Gain Privileges or Assume Identity
Using a key past its expiration data increases the timing window for cracking attacks against that key. Or, the key in question may be compromised, providing a malicious user with a method for authenticating as the victim.
Acknowledgements
Red Hat would like to thank Bruno Oliveira - abstractj (in collaboration with OpenAI) for reporting this issue.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.