CVE-2026-8922: Keycloak: Revoked Tokens Can Remain Active When Both Realm-Level and Client-Level `notBefore` Revocation Policies are Configured
(updated )
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
- access.redhat.com/errata/RHSA-2026:25097
- access.redhat.com/errata/RHSA-2026:25098
- access.redhat.com/security/cve/CVE-2026-8922
- bugzilla.redhat.com/show_bug.cgi?id=2479586
- github.com/advisories/GHSA-83c4-ffjp-mxp9
- github.com/keycloak/keycloak/commit/b6cd645683f469724cd588fac415fe09bd20a27a
- github.com/keycloak/keycloak/commit/c5bda802e98b412e42fa62ff6240669e9ea4a858
- github.com/keycloak/keycloak/issues/49118
- github.com/keycloak/keycloak/pull/49129
- nvd.nist.gov/vuln/detail/CVE-2026-8922
Code Behaviors & Features
Detect and mitigate CVE-2026-8922 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →