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.
Metrics
CVSS 3.1 6.8/10
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| Red Hat | Red Hat build of Keycloak 26.4 | — |
| Red Hat | Red Hat build of Keycloak 26.4 | — |
| 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 | — |
| Red Hat | Red Hat build of Keycloak 26.6 | — |
| Red Hat | Red Hat build of Keycloak 26.6.3 | — |
References
- 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-9802Vendor Advisory
- https://bugzilla.redhat.com/show_bug.cgi?id=2482467Issue Tracking, Vendor Advisory
Timeline
- Published
- May 28, 2026
- Last modified
- Oct 26, 2026
- NVD status
- Modified