CVE-2026-9802: Red Hat build of Keycloak 26.4 · Insufficient Session Expiration
Affects Red Hat build of Keycloak 26.4Source CVE Database V5
Not known to be exploited · CVSS 6.8 Medium.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red HatRed Hat build of Keycloak 26.4 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.4 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.4.13 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.6 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.6 | Affected– | Fixed in– |
| Red HatRed Hat build of Keycloak 26.6.3 | Affected– | Fixed in– |
AI-suggested
Red Hat has released updated Keycloak 26.6.3 images that address this vulnerability. Users should upgrade to these updated images to remediate the issue. Before applying the update, back up existing installations including applications, configuration files, and databases. No explicit patch for version 26.4 is provided; therefore, upgrading to the fixed 26.6.3 version is the recommended action. Monitor Red Hat advisories for any further updates or patches.
Description
A flaw was found in Keycloak. When revokeRefreshToken=true is enabled and persistent session storage is in use, a server restart can reset internal timing mechanisms. This allows a remote attacker, who has previously captured a user's refresh token, to replay that token even after it has been revoked. Successful exploitation grants the attacker unauthorized access to the victim's account, potentially leading to information disclosure or privilege escalation.
References
- access.redhat.com/errata/RHSA-2026:25097 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:25098 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:30049 (opens in a new tab)
- access.redhat.com/errata/RHSA-2026:30050 (opens in a new tab)
- access.redhat.com/security/cve/CVE-2026-9802 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2482467 (opens in a new tab)