Keycloak: Revoked Tokens Can Remain Active When Both Realm-Level and Client-Level `notBefore` Revocation Policies are Configured
GHSA-83c4-ffjp-mxp9 · CVE-2026-8922
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
A flaw was found in Keycloak. When both realm-level and client-level notBefore revocation policies are configured, Keycloak's OpenID Connect (OIDC) Introspection feature fails to properly honor the realm-level policy. This allows tokens that should have been revoked to remain active, potentially leading to unauthorized access or continued session validity. This could impact the security of systems utilizing Keycloak for identity and access management.
References
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-8922
- WEB https://github.com/keycloak/keycloak/issues/49118
- WEB https://github.com/keycloak/keycloak/pull/49129
- WEB https://github.com/keycloak/keycloak/commit/b6cd645683f469724cd588fac415fe09bd20a27a
- WEB https://github.com/keycloak/keycloak/commit/c5bda802e98b412e42fa62ff6240669e9ea4a858
- WEB https://access.redhat.com/errata/RHSA-2026:25097
- WEB https://access.redhat.com/errata/RHSA-2026:25098
- WEB https://access.redhat.com/errata/RHSA-2026:30049
- WEB https://access.redhat.com/errata/RHSA-2026:30050
- WEB https://access.redhat.com/security/cve/CVE-2026-8922
- WEB https://bugzilla.redhat.com/show_bug.cgi?id=2479586
- PACKAGE https://github.com/keycloak/keycloak
Ready to move
Start Securing
Free, no credit card | First findings in minutes