CVE-2026-9802Keycloak: keycloak: unauthorized account access via replayed refresh tokens after cluster restart
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.
Data: CVE.org, NVD, CISA KEV, FIRST EPSS, Ubuntu. Published as the sources state it, in English.
Affected products and versions
| Vendor | Product | Versions | |
|---|---|---|---|
| build keycloak | 26.4 | — | |
| build keycloak | 26.6 | — | |
| redhat | build of keycloak | — | |
| Red Hat | Red Hat build of Keycloak 26.4 | all versions | |
| Red Hat | Red Hat build of Keycloak 26.4.13 | — | |
| Red Hat | Red Hat build of Keycloak 26.6 | all versions | |
| Red Hat | Red Hat build of Keycloak 26.6.3 | — |
References and patches
- RHSA-2026:25097 vendor-advisory
- RHSA-2026:25098 vendor-advisory
- RHSA-2026:30049 vendor-advisory
- RHSA-2026:30050 vendor-advisory
- https://access.redhat.com/security/cve/CVE-2026-9802 vdb-entryVendor Advisory
- RHBZ#2482467 issue-trackingIssue TrackingVendor Advisory
CPE matches (NVD) (1)
cpe:2.3:a:redhat:build_of_keycloak:-:*:*:*:-:*:*:*