Analyst readout for executives and security teams
Plain-English summary
This Keycloak flaw can let an attacker reuse a refresh token that should have been revoked after a server or cluster restart. The attacker must already have captured a user's refresh token. If successful, they may access that user's account, creating confidentiality and integrity risk for identity-backed applications.
Executive priority
Treat as a moderate-priority identity security issue. It deserves prompt patch planning because compromised SSO sessions can expose many applications, but available evidence does not indicate active exploitation or broad unauthenticated compromise.
Technical view
With revokeRefreshToken=true and persistent session storage enabled, a restart can reset internal timing used to enforce refresh-token revocation. This creates a CWE-613 session expiration failure where a previously captured revoked refresh token may be accepted. Red Hat rates this CVSS 6.8, with high confidentiality and integrity impact but high attack complexity.
Likely exposure
Exposure is limited to Red Hat build of Keycloak 26.6 deployments matching the affected package versions and configuration conditions. Risk is higher for internet-facing identity services, clustered deployments, frequent restarts, and realms serving privileged users or sensitive applications.
Exploitation context
The bundle does not show CISA KEV listing or active exploitation evidence. Exploitation requires prior refresh-token capture, the vulnerable configuration, persistent session storage, and a restart condition that resets timing mechanisms. This is not described as a simple unauthenticated compromise path.
Researcher notes
Focus validation on the exact configuration: refresh-token revocation enabled, persistent sessions, and restart behavior. The key precondition is token capture before replay. Avoid assuming all Keycloak deployments are affected; the source bundle names Red Hat build of Keycloak 26.6 package variants.
Mitigation direction
- Review RHSA-2026:25097 and RHSA-2026:25098 for Red Hat's fixed build guidance.
- Upgrade affected Red Hat build of Keycloak packages to a vendor-designated unaffected version.
- Prioritize realms protecting administrative, privileged, or sensitive business applications.
- Reduce unnecessary restarts until patched where operationally feasible.
- Investigate and rotate credentials for users with suspected token exposure.
Validation and detection
- Inventory Red Hat build of Keycloak versions and package names against the affected list.
- Confirm whether revokeRefreshToken=true and persistent session storage are enabled.
- Review restart windows for clustered or highly available Keycloak deployments.
- Check authentication logs for unusual refresh activity after restarts.
- Validate remediation against Red Hat advisories, not only upstream Keycloak version strings.
Public sources used
Based on public source material and reviewed before publication.
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:N 1.6 5.2 redhat Vulnerability scoring details
Base CVSS 3.1 score
6.8 MediumVector: 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 timeline redhat
Reported to Red Hat.
- CVE reserved CVE Program
The CVE ID was reserved by the assigning CNA.
- Source timeline redhat
Made public.
- CVE published CVE Program
The CVE record was published.
- CVE updated CVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 source CVE List V5
- RHSA-2026:25097 CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- RHSA-2026:25098 CVE reference, redhat · vendor-advisory, x_refsource_REDHAT
- https://access.redhat.com/security/cve/CVE-2026-9802 CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2482467 CVE 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.