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.
References
| Link | Resource |
|---|---|
| https://access.redhat.com/security/cve/CVE-2026-9802 | Vendor Advisory |
| https://bugzilla.redhat.com/show_bug.cgi?id=2482467 | Issue Tracking Vendor Advisory |
Configurations
History
03 Jun 2026, 19:36
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://access.redhat.com/security/cve/CVE-2026-9802 - Vendor Advisory | |
| References | () https://bugzilla.redhat.com/show_bug.cgi?id=2482467 - Issue Tracking, Vendor Advisory | |
| CPE | cpe:2.3:a:redhat:build_of_keycloak:-:*:*:*:-:*:*:* | |
| First Time |
Redhat
Redhat build Of Keycloak |
28 May 2026, 06:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-05-28 06:16
Updated : 2026-06-03 19:36
NVD link : CVE-2026-9802
Mitre link : CVE-2026-9802
CVE.ORG link : CVE-2026-9802
JSON object : View
Products Affected
redhat
- build_of_keycloak
CWE
CWE-613
Insufficient Session Expiration
