Security readout for executives and security teams
Plain-English summary
This Keycloak flaw can let a previously stolen refresh token work again after a server or cluster restart, even if it was revoked. It affects certain Red Hat build of Keycloak 26.4 and 26.6 packages when refresh-token revocation and persistent session storage are used.
Executive priority
Treat as a priority identity-platform update, especially for production SSO handling sensitive systems. The flaw is not reported as actively exploited, but stolen tokens could regain value after restarts in affected configurations.
Technical view
CVE-2026-9802 is a CWE-613 session expiration issue. With revokeRefreshToken=true and persistent session storage, restart behavior can reset internal timing, allowing replay of a captured revoked refresh token. CVSS 3.1 is 6.8, with high confidentiality and integrity impact, no privileges required, high attack complexity, and user interaction required.
Likely exposure
Exposure is most relevant for organizations running affected Red Hat build of Keycloak 26.4 or 26.6 in clustered or restarted environments with persistent session storage and refresh-token revocation enabled.
Exploitation context
No provided source or KEV listing indicates active exploitation. Abuse requires a previously captured user refresh token plus the vulnerable configuration and restart condition. Successful exploitation may allow unauthorized account access, information disclosure, or privilege escalation through the victim account.
Researcher notes
The source data lists affected package entries and separate unaffected product-version entries for 26.4.13 and 26.6.3. Confirm exact fixed builds through the RHSA pages before closure. Do not assume all upstream Keycloak versions are affected from this record alone.
Mitigation direction
- Review the Red Hat advisories linked for affected packages and fixed guidance.
- Update affected Red Hat build of Keycloak packages per Red Hat guidance.
- Confirm whether revokeRefreshToken=true and persistent session storage are in use.
- Prioritize environments where Keycloak protects privileged or sensitive applications.
- Handle known token theft events as potentially higher risk until remediated.
Validation and detection
- Inventory Red Hat build of Keycloak 26.4 and 26.6 deployments.
- Compare installed packages against Red Hat advisory affected and unaffected entries.
- Check Keycloak configuration for refresh-token revocation and persistent session storage.
- Review restart windows against suspicious refresh-token or session activity.
- Confirm remediation status using Red Hat errata and vendor tooling.
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-613: 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 lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-9802 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
- 6.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/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:H/PR:N/UI:R/S:U/C:H/I:H/A:N1.65.2redhatVulnerability scoring details
Base CVSS 3.1 score
6.8MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/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-9802CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2482467CVE 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.
Insufficient Session Expiration
Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.