CVE-2026-18218: Missing Authorization in Red Hat Red Hat Build of Keycloak
A flaw was found in the TokenManager component of the Keycloak identity management service. When an administrator attempts to revoke tokens for a specific application (client) using a "not-before" policy, the revocation may be silently ignored if the overall security realm already has an older, non-zero revocation policy in place. This issue can allow previously issued tokens to remain valid for refreshing sessions and accessing user information even after an administrator has attempted to invalidate them. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
AI Analysis
Technical Summary
CVE-2026-18218 is a logic flaw in the TokenManager.NotBeforeCheck function of Red Hat Build of Keycloak. When an administrator tries to revoke tokens for a client using a "not-before" policy, the revocation may be ignored if the realm-level not-before policy is older but non-zero. This causes client-specific token revocations to be ineffective, allowing previously issued tokens to remain valid for refresh, introspection, and UserInfo requests. The issue arises from improper enforcement of client-specific revocation policies when a realm-level policy exists. Exploitation requires possession of valid tokens and a particular realm configuration. Red Hat rates this vulnerability as moderate severity and has not provided a patch or effective mitigation at this time.
Potential Impact
An attacker with valid tokens issued within a specific timeframe and under a specific realm configuration can continue to use revoked tokens to refresh sessions and access user information. This results in confidentiality and integrity impacts by allowing unauthorized access and modification of application data. The vulnerability does not impact availability. The overall severity is medium (CVSS 4.2).
Mitigation Recommendations
Currently, no mitigation or patch meeting Red Hat Product Security criteria for ease of use, applicability, and stability is available. Administrators should monitor Red Hat advisories for updates. No immediate action is recommended by Red Hat beyond awareness of the issue.
CVE-2026-18218: Missing Authorization in Red Hat Red Hat Build of Keycloak
Description
A flaw was found in the TokenManager component of the Keycloak identity management service. When an administrator attempts to revoke tokens for a specific application (client) using a "not-before" policy, the revocation may be silently ignored if the overall security realm already has an older, non-zero revocation policy in place. This issue can allow previously issued tokens to remain valid for refreshing sessions and accessing user information even after an administrator has attempted to invalidate them. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVSS v3.1
Score 4.2medium
Affected software
Red Hat
Red Hat Build of Keycloak
Red Hat
Red Hat Data Grid 8
Red Hat
Red Hat JBoss Enterprise Application Platform Expansion Pack
Red Hat
Red Hat Single Sign-On 7
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-18218 is a logic flaw in the TokenManager.NotBeforeCheck function of Red Hat Build of Keycloak. When an administrator tries to revoke tokens for a client using a "not-before" policy, the revocation may be ignored if the realm-level not-before policy is older but non-zero. This causes client-specific token revocations to be ineffective, allowing previously issued tokens to remain valid for refresh, introspection, and UserInfo requests. The issue arises from improper enforcement of client-specific revocation policies when a realm-level policy exists. Exploitation requires possession of valid tokens and a particular realm configuration. Red Hat rates this vulnerability as moderate severity and has not provided a patch or effective mitigation at this time.
Potential Impact
An attacker with valid tokens issued within a specific timeframe and under a specific realm configuration can continue to use revoked tokens to refresh sessions and access user information. This results in confidentiality and integrity impacts by allowing unauthorized access and modification of application data. The vulnerability does not impact availability. The overall severity is medium (CVSS 4.2).
Mitigation Recommendations
Currently, no mitigation or patch meeting Red Hat Product Security criteria for ease of use, applicability, and stability is available. Administrators should monitor Red Hat advisories for updates. No immediate action is recommended by Red Hat beyond awareness of the issue.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- redhat
- Date Reserved
- 2026-07-29T09:00:23.659Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-18218","vendor":"Red Hat"}]
Threat ID: 6a6c50cf9c2644c7f87f9881
Added to database: 07/31/2026, 07:37:51 UTC
Last enriched: 08/07/2026, 14:50:13 UTC
Last updated: 09/13/2026, 10:01:29 UTC
Views: 59
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.