dbcve.org
Build Of KeycloakApplication · Redhat

CVE-2026-8922

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

In Keycloak, when both realm-level and client-level notBefore revocation policies are configured, the OIDC Introspection endpoint fails to properly enforce the realm-level policy. This causes tokens that should be revoked according to the realm-level notBefore timestamp to remain active and return as valid during introspection, creating a window for continued unauthorized access.

MitigationReview current notBefore policy configurations and consider removing client-level overrides until the fix is applied. Monitor for suspicious session activity and implement additional authentication controls for sensitive operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Build Of KeycloakApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Keycloak deployment in your environment
    Identify all Keycloak instances running in your infrastructure and note the version of Red Hat Build of Keycloak being used.
    Affected if Any version of Red Hat Build of Keycloak is deployed.
  2. Identify OIDC Introspection endpoint usage
    Review your applications and services that rely on Keycloak's OIDC introspection endpoint (typically /realms/{realm}/protocol/openid-connect/token/introspect) for token validation.
    Affected if Your applications use the introspection endpoint for token validation.
  3. Check for realm-level notBefore policy configuration
    Access Keycloak admin console or use admin API to inspect the realm settings. Navigate to the realm where OIDC clients are configured and check if a notBefore timestamp is set at the realm level under Realm Settings > Tokens > Not Before.
    Affected if A realm-level notBefore policy is configured.
  4. Check for client-level notBefore policy configuration
    In Keycloak admin console, go to each client's settings and inspect the Client settings > Advanced > Not Before field to determine if any OAuth clients have a client-specific notBefore timestamp configured.
    Affected if At least one client has a client-level notBefore policy configured.
  5. Confirm simultaneous policy configuration
    Cross-reference results from steps 3 and 4. Determine if BOTH realm-level notBefore AND at least one client-level notBefore are configured concurrently in the same realm.
    Affected if Both realm-level and client-level notBefore policies are configured at the same time.

You are affected if you are running Red Hat Build of Keycloak with both realm-level and client-level notBefore revocation policies configured simultaneously, as the introspection endpoint will fail to properly enforce the realm-level policy in this configuration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Review current notBefore policy configurations and consider removing client-level overrides until the fix is applied. Monitor for suspicious session activity and implement additional authentication controls for sensitive operations.

Fix this in Build Of Keycloak Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8922 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8922 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data