Keycloak does not validate and update refresh token usage atomically
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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-1035US | — | — | ||
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… | ||||
references
External citations — patches, advisories, analysis.
- https://access.redhat.com/errata/RHSA-2026:6477WEB
- https://access.redhat.com/errata/RHSA-2026:6478WEB
- https://access.redhat.com/security/cve/CVE-2026-1035WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=2430314WEB
- https://github.com/keycloak/keycloakPACKAGE
- https://github.com/keycloak/keycloak/issues/45647WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-1035ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan