Security readout for executives and security teams
Plain-English summary
Keycloak may treat some revoked OIDC tokens as still active when both realm-level and client-level notBefore revocation policies are configured. The business risk is continued access after a token should have been invalidated, especially for systems depending on Keycloak token introspection for authorization decisions.
Executive priority
Prioritize remediation for Keycloak environments protecting sensitive applications, especially where token revocation is used after account compromise, employee offboarding, or incident response. This is not currently evidenced as exploited, but failed revocation can undermine access removal controls.
Technical view
The flaw affects Keycloak OIDC Introspection handling. With both realm and client notBefore policies present, introspection may fail to honor the realm-level revocation policy, so tokens that should be inactive can validate as active. Red Hat rates this CVSS 5.4, network-accessible, low complexity, requiring low privileges.
Likely exposure
Exposure is most likely in Red Hat build of Keycloak 26.4 and 26.6 deployments using OIDC introspection plus both realm-level and client-level notBefore revocation policies. The provided data names affected RHBK packages and indicates some 26.4.13 and 26.6.3 entries as unaffected.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation. Exploitation would require a context where an attacker has or can obtain a token that should be revoked, and where relying services accept Keycloak introspection results.
Researcher notes
The key condition is combined realm-level and client-level notBefore policy use with OIDC Introspection. Evidence in the bundle is sufficient for affected product scope and impact, but it does not include exploit details, proof-of-concept status, or complete fixed package mapping.
Mitigation direction
- Review the Red Hat RHSA advisories for your exact RHBK stream and package.
- Apply vendor-provided Keycloak updates where Red Hat marks your package affected.
- Inventory clients that rely on OIDC introspection for authorization decisions.
- Review realm and client notBefore revocation policy usage until patched.
- If no matching fix is clear, open a Red Hat support case for guidance.
Validation and detection
- Check deployed Red Hat build of Keycloak version and package identifiers.
- Confirm whether both realm-level and client-level notBefore policies are configured.
- Identify applications that trust Keycloak introspection responses for active-token decisions.
- After updating, verify revoked tokens are rejected by dependent applications.
- Track RHSA-2026:25097, 25098, 30049, and 30050 for package status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-303: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-8922 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N2.82.5redhatVulnerability scoring details
Base CVSS 3.1 score
5.4MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineredhat
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2026:25097CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:25098CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:30049CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:30050CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-8922CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2479586CVE reference, redhat · issue-tracking, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Implementation of Authentication Algorithm
Incorrect Implementation of Authentication Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.