Skip to content
Fencer Intel
medium 6.8

CVE-2026-9802 json

Keycloak: keycloak: unauthorized account access via replayed refresh tokens after cluster restart

published 5mo ago modified 16d ago also GHSA-v5g5-wwmp-jppw , EUVD-2026-32720

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.keycloak:keycloak-services 26.6.3
  • Red Hat Red Hat build of Keycloak 26.4 26.4-19, 26.4.13-1
  • Red Hat Red Hat build of Keycloak 26.6 26.6-6, 26.6.3-3

Is CVE-2026-9802 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-9802 updated cvss 6.8

keycloak: Keycloak: Unauthorized account access via replayed refresh tokens after cluster restart

  • Red Hat build of Keycloak 26.4 rhbk/keycloak-rhel9 26.4-19, rhbk/keycloak-rhel9-operator 26.4-19, rhbk/keycloak-operator-bundle 26.4.13-1
    fixed: vendor fix RHSA-2026:30050
  • Red Hat build of Keycloak 26.4.13
    fixed: vendor fix RHSA-2026:30049
  • Red Hat build of Keycloak 26.6 rhbk/keycloak-rhel9 26.6-6, rhbk/keycloak-rhel9-operator 26.6-6, rhbk/keycloak-operator-bundle 26.6.3-3
    fixed: vendor fix RHSA-2026:25097
  • Red Hat build of Keycloak 26.6.3
    fixed: vendor fix RHSA-2026:25098

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
5mo ago

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
GitHub 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
maven org.keycloak:keycloak-services
<=26.4.7
>=26.5.0, <26.6.3
26.6.3

Affected products

  • Red Hat Red Hat build of Keycloak 26.4
  • Red Hat Red Hat build of Keycloak 26.4.13
  • Red Hat Red Hat build of Keycloak 26.6
  • Red Hat Red Hat build of Keycloak 26.6.3

Classification

Weakness
  • CWE-613 DEPRECATED: Insufficient Session Expiration

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.