Advisory Database
  • Advisories
  • Dependency Scanning
  1. maven
  2. ›
  3. org.keycloak/keycloak-services
  4. ›
  5. CVE-2026-1035

CVE-2026-1035: Keycloak does not validate and update refresh token usage atomically

January 21, 2026

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

  • access.redhat.com/security/cve/CVE-2026-1035
  • bugzilla.redhat.com/show_bug.cgi?id=2430314
  • github.com/advisories/GHSA-m2w5-7xhv-w6fh
  • github.com/keycloak/keycloak
  • github.com/keycloak/keycloak/issues/45647
  • nvd.nist.gov/vuln/detail/CVE-2026-1035

Code Behaviors & Features

Detect and mitigate CVE-2026-1035 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →

Affected versions

All versions up to 26.2.5

Solution

Unfortunately, there is no solution available yet.

Impact 3.1 LOW

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

Learn more about CVSS

Weakness

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

Source file

maven/org.keycloak/keycloak-services/CVE-2026-1035.yml

Spotted a mistake? Edit the file on GitLab.

  • Site Repo
  • About GitLab
  • Terms
  • Privacy Statement
  • Contact

Page generated Wed, 04 Feb 2026 00:36:09 +0000.