Keycloak has Insufficient Session Expiration
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-9802US | — | — | ||
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2026:25097WEB
- https://access.redhat.com/errata/RHSA-2026:25098WEB
- https://access.redhat.com/errata/RHSA-2026:30049WEB
- https://access.redhat.com/errata/RHSA-2026:30050WEB
- https://access.redhat.com/security/cve/CVE-2026-9802WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2482467WEB
- https://github.com/keycloak/keycloakPACKAGE
- https://github.com/keycloak/keycloak/commit/165df48d3f0f42ede8e6082184892ca7cc703989WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan