Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-m2w5-7xhv-w6fh

Keycloak does not validate and update refresh token usage atomically

CVSS 3.1 LowEPSS 0.0030 · 23rd percentile

Published by the GitHub Advisory Database at 21 Jan 2026, 06:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
org.keycloak:keycloak-servicesMaven<=26.2.5No fixed version yet
Identifiers
GHSA-m2w5-7xhv-w6fh · CVE-2026-1035
Weakness (CWE)
CWE-367
Tags
Published
21 Jan 2026
Updated
2 Apr 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Keycloak's keycloak-services package, versions up to and including 26.2.5, is affected. When strict refresh token rotation is enabled, concurrent refresh requests can bypass single-use enforcement, so one refresh token can be used to issue multiple access tokens. The source does not say what access an attacker needs. No fixed version is listed, and the source gives no workaround.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
3.1 Low 3.1 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.0030, the 23rd percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:20 UTC First seen by agentprime
  2. 31 Oct 2026, 14:20 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.