No advisories yet.
Solution
No solution given by the vendor.
Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Thu, 28 May 2026 06:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Keycloak: keycloak: unauthorized account access via replayed refresh tokens after cluster restart | |
| First Time appeared |
Redhat
Redhat build Keycloak |
|
| Weaknesses | CWE-613 | |
| CPEs | cpe:/a:redhat:build_keycloak: | |
| Vendors & Products |
Redhat
Redhat build Keycloak |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-05-28T04:47:10.497Z
Reserved: 2026-05-28T04:02:07.242Z
Link: CVE-2026-9802
No data.
Status : Received
Published: 2026-05-28T06:16:29.620
Modified: 2026-05-28T06:16:29.620
Link: CVE-2026-9802
No data.
OpenCVE Enrichment
Updated: 2026-05-28T07:30:11Z