Token-revocation bypass via misordered not-before comparison
Published Jul 31, 2026 · Updated Jul 31, 2026
Token-revocation bypass in Red Hat build of Keycloak allows remote authenticated users to keep using client tokens after revocation. TokenManager.NotBeforeCheck prioritizes an older nonzero realm not-before timestamp over a newer client timestamp, so it fails to enforce the client policy. Exploitation requires that realm state and a valid OIDC token issued after the realm timestamp but before client revocation; refresh, introspection, and UserInfo requests remain accepted.
Summary
What happened
Token-revocation bypass in Red Hat build of Keycloak allows remote authenticated users to keep using client tokens after revocation. TokenManager.NotBeforeCheck prioritizes an older nonzero realm not-before timestamp over a newer client timestamp, so it fails to enforce the client policy. Exploitation requires that realm state and a valid OIDC token issued after the realm timestamp but before client revocation; refresh, introspection, and UserInfo requests remain accepted.
The record
- CVE
- CVE-2026-18218
- Published
- Jul 31, 2026
- Updated
- Jul 31, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat build of Keycloak
- Classifications
- CWE-862, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 31, 2026CVE publishedPublication date reported by the CVE source.
- Jul 31, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo