A flaw was found in the TokenManager component of the Keycloak identity management service. (CVE-2026-18218)
A vulnerability in the TokenManager component of the Keycloak identity management service allows token revocation attempts for specific clients to be silently ignored if an older, non-zero realm-level revocation policy exists. This flaw permits previously issued tokens to remain valid for session refresh and user information access despite administrator revocation attempts. The issue arises from a logic error in enforcing client-specific revocation policies when a realm-level policy is present. Exploitation requires a specific realm configuration and possession of valid tokens within a certain timeframe. No effective mitigation or patch is currently available according to the vendor advisory.
AI Analysis
Technical Summary
CVE-2026-18218 is a moderate severity vulnerability in Keycloak's TokenManager component. When an administrator tries to revoke tokens for a particular client using a "not-before" policy, the revocation can be silently ignored if the security realm already has an older, non-zero revocation policy. This logic error in the TokenManager.NotBeforeCheck function causes client-specific revocation policies to be bypassed in favor of the older realm-level policy. As a result, tokens previously issued may continue to be used for session refresh, introspection, and accessing user information even after revocation attempts. Exploitation requires low privileges but a specific pre-existing realm configuration and possession of valid tokens. Red Hat's advisory confirms no current mitigation or fix meets their criteria for deployment.
Potential Impact
The vulnerability allows attackers who possess valid tokens and have knowledge of a specific realm configuration to continue using revoked tokens for refreshing sessions, introspection, and accessing user information. This leads to unauthorized access to sensitive data and potential privilege escalation by bypassing intended token revocation controls. The impact is limited to confidentiality and integrity with no availability impact. Exploitation complexity is high due to required conditions, and no known exploits are reported in the wild.
Mitigation Recommendations
According to the Red Hat advisory, no effective mitigation or patch is currently available that meets criteria for ease of use, deployment, or applicability. Administrators should be aware of the issue and monitor vendor communications for future fixes. Until a fix is released, cautious management of token revocation policies and minimizing token exposure are advisable, but no direct mitigation is provided by the vendor.
A flaw was found in the TokenManager component of the Keycloak identity management service. (CVE-2026-18218)
Description
A vulnerability in the TokenManager component of the Keycloak identity management service allows token revocation attempts for specific clients to be silently ignored if an older, non-zero realm-level revocation policy exists. This flaw permits previously issued tokens to remain valid for session refresh and user information access despite administrator revocation attempts. The issue arises from a logic error in enforcing client-specific revocation policies when a realm-level policy is present. Exploitation requires a specific realm configuration and possession of valid tokens within a certain timeframe. No effective mitigation or patch is currently available according to the vendor advisory.
CVSS v3.1
Score 4.2medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-18218 is a moderate severity vulnerability in Keycloak's TokenManager component. When an administrator tries to revoke tokens for a particular client using a "not-before" policy, the revocation can be silently ignored if the security realm already has an older, non-zero revocation policy. This logic error in the TokenManager.NotBeforeCheck function causes client-specific revocation policies to be bypassed in favor of the older realm-level policy. As a result, tokens previously issued may continue to be used for session refresh, introspection, and accessing user information even after revocation attempts. Exploitation requires low privileges but a specific pre-existing realm configuration and possession of valid tokens. Red Hat's advisory confirms no current mitigation or fix meets their criteria for deployment.
Potential Impact
The vulnerability allows attackers who possess valid tokens and have knowledge of a specific realm configuration to continue using revoked tokens for refreshing sessions, introspection, and accessing user information. This leads to unauthorized access to sensitive data and potential privilege escalation by bypassing intended token revocation controls. The impact is limited to confidentiality and integrity with no availability impact. Exploitation complexity is high due to required conditions, and no known exploits are reported in the wild.
Mitigation Recommendations
According to the Red Hat advisory, no effective mitigation or patch is currently available that meets criteria for ease of use, deployment, or applicability. Administrators should be aware of the issue and monitor vendor communications for future fixes. Until a fix is released, cautious management of token revocation policies and minimizing token exposure are advisable, but no direct mitigation is provided by the vendor.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-vhxw-j6h3-48jm
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-18218"]
- Ecosystems
- []
- Database Specific Severity
- MODERATE
- Cvss Version
- 3.1
Threat ID: 6a7742a8bf8831d539b08c0a
Added to database: 08/08/2026, 14:52:24 UTC
Last enriched: 08/08/2026, 15:19:09 UTC
Last updated: 08/09/2026, 00:41:12 UTC
Views: 3
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.