Keycloak on Red Hat Refresh Token session expiration

Summaryinfo

A vulnerability, which was classified as problematic, was found in Keycloak on Red Hat. This vulnerability affects unknown code of the component Refresh Token Handler. Such manipulation leads to session expiration. This vulnerability is listed as CVE-2026-9802. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability was found in Keycloak on Red Hat (affected version not known). It has been rated as problematic. Affected by this issue is some unknown functionality of the component Refresh Token Handler. The manipulation with an unknown input leads to a session expiration vulnerability. Using CWE to declare the problem leads to CWE-613. According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization." Impacted is confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is available at access.redhat.com. This vulnerability is handled as CVE-2026-9802 since 05/28/2026. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 05/28/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-32720). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• Keycloak

License

• open-source

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion