CVE-2026-9802

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure, data tampering.

Exploit odds

0.3% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-05-28 06:16 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-26 12:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.3% in the next 30 days (EPSS).
• Severity: 6.8 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-05-28 06:16 UTC

Last modified

2026-10-26 12:10 UTC

Exploit probability

0.3% · EPSS, next 30 days

Weakness

CWE-613

Record status

Modified

Affected

• Redhat Build Of Keycloak

Attack profile CVSS 3.1 · 6.8

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-9802.md and follow it. Check whether this project is affected by CVE-2026-9802. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge