Org.keycloak.protocol.oidc: keycloak refresh token reuse bypass via toctou race condition
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Red Hat | Red Hat build of Keycloak 26.4 | affected |
|
||||||
| Red Hat | Red Hat build of Keycloak 26.4 | affected |
|
||||||
| Red Hat | Red Hat build of Keycloak 26.4 | affected |
|
||||||
| Red Hat | Red Hat build of Keycloak 26.4.11 | unaffected | — | ||||||
| Red Hat | Red Hat JBoss Enterprise Application Platform 8 | unaffected | — | ||||||
| Red Hat | Red Hat JBoss Enterprise Application Platform Expansion Pack | unaffected | — | ||||||
| Red Hat | Red Hat Single Sign-On 7 | unaffected | — |
No data.
No data.
No data available yet.
Vendor Workaround
To mitigate this issue, configure the `refreshTokenMaxReuse` policy in Keycloak to a value greater than zero. This prevents the race condition by allowing a limited number of reuses for refresh tokens, thereby maintaining the integrity of the Refresh Token Rotation hardening measure. Consult Keycloak documentation for specific configuration instructions. Changes to Keycloak configuration typically require a service restart or redeployment to take effect.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-m2w5-7xhv-w6fh | Keycloak does not validate and update refresh token usage atomically |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.303% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:/a:redhat:build_keycloak:26.4::el9 | |
| References |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Org.keycloak.protocol.oidc: keycloak refresh token reuse bypass via toctou race condition | |
| First Time appeared |
Redhat
Redhat build Keycloak Redhat jboss Enterprise Application Platform Redhat jbosseapxp Redhat red Hat Single Sign On |
|
| Weaknesses | CWE-367 | |
| CPEs | cpe:/a:redhat:build_keycloak: cpe:/a:redhat:jboss_enterprise_application_platform:8 cpe:/a:redhat:jbosseapxp cpe:/a:redhat:red_hat_single_sign_on:7 |
|
| Vendors & Products |
Redhat
Redhat build Keycloak Redhat jboss Enterprise Application Platform Redhat jbosseapxp Redhat red Hat Single Sign On |
|
| References |
| |
| Metrics |
cvssV3_1
|