Keycloak does not validate and update refresh token usage atomically
GHSA-m2w5-7xhv-w6fh · CVE-2026-1035
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
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.
References
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-1035
- WEB 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
- PACKAGE https://github.com/keycloak/keycloak
Ready to move
Start Securing
Free, no credit card | First findings in minutes