CVE-2026-9802
Keycloak: keycloak: unauthorized account access via replayed refresh tokens after cluster restart
Vexday Risk Score
13Low
SSVC decision (CISA)
Track
No exploitation signal → monitor
CVSS 6.8EPSS 0.3%KEV nãoPoC —Nuclei —Metasploit —Patch referenciado
Lifecycle
28 May 2026Published on NVD
Recommendation: Monitor — no exploitation signal at the moment.
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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
Affected products
Red Hat · Red Hat build of Keycloak 26.4Red Hat · Red Hat build of Keycloak 26.4.13Red Hat · Red Hat build of Keycloak 26.6Red Hat · Red Hat build of Keycloak 26.6.3Want to know if your infrastructure is exposed to this?
Talk to TrueHacking →References
https://access.redhat.com/errata/RHSA-2026:25097https://access.redhat.com/errata/RHSA-2026:25098https://access.redhat.com/errata/RHSA-2026:30049https://access.redhat.com/errata/RHSA-2026:30050https://access.redhat.com/security/cve/CVE-2026-9802https://bugzilla.redhat.com/show_bug.cgi?id=2482467