Home

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.

PUBLISHED Reserved 2026-05-28 | Published 2026-05-28 | Updated 2026-05-28 | Assigner redhat




MEDIUM: 6.8CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N

Problem types

Insufficient Session Expiration

Product status

Default status
affected

Timeline

2026-05-28:Reported to Red Hat.
2026-05-28:Made public.

Credits

Red Hat would like to thank Gyeongpyo Son for reporting this issue.

References

access.redhat.com/security/cve/CVE-2026-9802 vdb-entry

bugzilla.redhat.com/show_bug.cgi?id=2482467 (RHBZ#2482467) issue-tracking

cve.org (CVE-2026-9802)

nvd.nist.gov (CVE-2026-9802)

Download JSON