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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4.13-1 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-19 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-19 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4.13
Default version status: unaffected
Red Hat Red Hat build of Keycloak 26.6
Default version status: affected
26.6.3-3 to < *unaffected
Red Hat Red Hat build of Keycloak 26.6
Default version status: affected
26.6-6 to < *unaffected
Red Hat Red Hat build of Keycloak 26.6
Default version status: affected
26.6-6 to < *unaffected
Red Hat Red Hat build of Keycloak 26.6.3
Default version status: unaffected
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-9802 ↗
- https://bugzilla.redhat.com/show_bug.cgi?id=2482467 ↗