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 products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4.11-1 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-14 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4
Default version status: affected
26.4-14 to < *unaffected
Red Hat Red Hat build of Keycloak 26.4.11
Default version status: unaffected
Red Hat Red Hat JBoss Enterprise Application Platform 8
Default version status: unaffected
Red Hat Red Hat JBoss Enterprise Application Platform Expansion Pack
Default version status: unaffected
Red Hat Red Hat Single Sign-On 7
Default version status: unaffected