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.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://access.redhat.com/security/cve/CVE-2026-9802 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2482467 Issue Tracking, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.8 · redhatNVD modified 2026-10-26 12:10
Affected (CPE criteria) 1
cpe:2.3:a:redhat:build_of_keycloak:-:*:*:*:-:*:*:*
References 6
- https://access.redhat.com/errata/RHSA-2026:25097
- https://access.redhat.com/errata/RHSA-2026:25098
- https://access.redhat.com/errata/RHSA-2026:30049
- https://access.redhat.com/errata/RHSA-2026:30050
- https://access.redhat.com/security/cve/CVE-2026-9802 Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2482467 Issue Tracking, Vendor Advisory