GHSA-m2w5-7xhv-w6fh
Keycloak does not validate and update refresh token usage atomically
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Maven | org.keycloak:keycloak-services | <= 26.2.5 | no fix listed |
Details
As written in the advisory (Markdown source, shown as plain text).
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.
References
External links from the advisory. They lead to third-party sites.
- https://nvd.nist.gov/vuln/detail/CVE-2026-1035
- https://github.com/keycloak/keycloak/issues/45647
- https://access.redhat.com/errata/RHSA-2026:6477
- https://access.redhat.com/errata/RHSA-2026:6478
- https://access.redhat.com/security/cve/CVE-2026-1035
- https://bugzilla.redhat.com/show_bug.cgi?id=2430314
- https://github.com/keycloak/keycloak