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. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Affected products
redhat: build of keycloak
References4
- access.redhat.com/security/cve/CVE-2026-18218 Vendor Advisory
- bugzilla.redhat.com/show_bug.cgi?id=2508313 Issue TrackingVendor Advisory
- access.redhat.com/errata/RHSA-2026:68277
- access.redhat.com/errata/RHSA-2026:68278
Metrics
- CVSS 3.1
-
5.4
MEDIUM
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N - EPSS — exploit probability
- 0% percentile: 22 · as of 13 November 2026
- CWE
- CWE-862
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.