REDHAT-BUG-2482467
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 Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2482467?
The severity of REDHAT-BUG-2482467 is classified as medium (4).
How do I fix REDHAT-BUG-2482467?
To fix REDHAT-BUG-2482467, review the configuration of Keycloak and ensure revokeRefreshToken is managed properly without relying on persistent session storage during restarts.
What is the impact of REDHAT-BUG-2482467?
The impact of REDHAT-BUG-2482467 is that an attacker can replay captured refresh tokens after a server restart, despite them being revoked.
Who is affected by REDHAT-BUG-2482467?
REDHAT-BUG-2482467 affects users of Keycloak who have enabled revokeRefreshToken and are using persistent session storage.
When was REDHAT-BUG-2482467 published?
REDHAT-BUG-2482467 was published on May 28, 2026.