GitHub Advisoryadvisory · Maven

GHSA-m2w5-7xhv-w6fh Keycloak does not validate and update refresh token usage atomically

LOW Published 2026-01-21 Modified 2026-04-02 Official page ↗
Aliases
CVE-2026-1035
Ecosystem
Maven
Packages
org.keycloak:keycloak-services
Severity
Low
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N
Weaknesses
CWE-367
Reviewed
2026-01-21

Affected packages

• Maven org.keycloak:keycloak-services: <= 26.2.5 (no fix yet)

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.

Related

Alias · CVE (1)

  • CVE-2026-1035 A flaw was found in the Keycloak server during refresh token processing, specifically in the TokenManager class responsible for enforcing… vulnerability

Weakness · CWE (1)

  • CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition weakness

References