GHSA-m2w5-7xhv-w6fh
Keycloak does not validate and update refresh token usage atomically
At a glance
- Published
- Updated
- CVE
- CVE-2026-1035
- CVSS_V3
- CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Description
A flaw was found in the Keycloak server during refresh token processing, specifically in the TokenManager class responsible for enforcing refresh token reuse policies. When strict refresh token rotation is enabled, the validation and update of refresh token usage are not performed atomically. This allows concurrent refresh requests to bypass single-use enforcement and issue multiple access tokens from the same refresh token. As a result, Keycloak’s refresh token rotation hardening can be undermined.
Affected packages
| Package | Versions |
|---|---|
| Maven · org.keycloak:keycloak-services | introduced 0, last affected 26.2.5 |
References
- https://nvd.nist.gov/vuln/detail/CVE-2026-1035 ADVISORY
- https://github.com/keycloak/keycloak/issues/45647 WEB
- https://access.redhat.com/errata/RHSA-2026:6477 WEB
- https://access.redhat.com/errata/RHSA-2026:6478 WEB
- https://access.redhat.com/security/cve/CVE-2026-1035 WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2430314 WEB
- https://github.com/keycloak/keycloak PACKAGE
Sources
| Source | Licence |
|---|---|
| OSV.dev | CC-BY 4.0 — GitHub Advisory Database |