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
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| Red Hat | Red Hat build of Keycloak 26.6 | — | — |
| Red Hat | Red Hat build of Keycloak 26.6.7 | — | — |
| 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 | — | — |
Advisories 1
- WID-SEC-2026-2614 Keycloak: Mehrere Schwachstellen BSI CERT-Bund (WID) · Nov 8, 2026
References
- RHSA-2026:68277 vendor-advisory
- RHSA-2026:68278 vendor-advisory
- https://access.redhat.com/security/cve/CVE-2026-18218 vdb-entry
- RHBZ#2508313 issue-tracking