CoreCVE
Back

MEDIUM

Keycloak: keycloak: unauthorized account access via replayed refresh tokens after cluster restart

Published May 28, 2026

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

Remediation

Vendor solution

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.

Red Hat statement

A flaw in Keycloak, when configured with `revokeRefreshToken=true` and persistent session storage, allows a remote attacker to regain unauthorized access. Following a full cluster restart, a previously revoked refresh token, if captured by an attacker, can be replayed to bypass security checks. This could lead to unauthorized account access, potentially resulting in information disclosure or privilege escalation.

Red Hat mitigation

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.

Metrics

Weaknesses (1)

CWE-613

References (16)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner redhat
Published May 28, 2026
Updated Jun 26, 2026
Reserved May 28, 2026
Link CVE-2026-9802
CISA Vulnrichment
Updated May 28, 2026
NVD
Status Modified
Modified Jun 26, 2026
Link CVE-2026-9802
Red Hat
Severity Moderate
Public date May 28, 2026
Links CVE-2026-9802 - Bugzilla
GHSA-V5G5-WWMP-JPPW