Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-86wq-234q-r6wg

Spring Cloud Config Server Susceptible To TOCTOU Attack

CVSS 7.4 HighEPSS 0.0022 · 12th percentile

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

PackageEcosystemAffectedFixed in
org.springframework.cloud:spring-cloud-config-serverMaven>=3.1.0, <=3.1.13 || >=4.1.0, <=4.1.9 || >=4.2.0, <=4.2.6 || >=4.3.0, <4.3.3 || >=5.0.0, <5.0.3 || >=3.0.0, <=3.0.74.3.3, 5.0.3
Identifiers
GHSA-86wq-234q-r6wg · CVE-2026-41002
Weakness (CWE)
CWE-367
Tags
Published
7 May 2026
Updated
18 Jun 2026

Machine-written summary

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

Spring Cloud Config Server versions 3.0.0 through 3.0.7, 3.1.0 through 3.1.13, 4.1.0 through 4.1.9, 4.2.0 through 4.2.6, 4.3.0 through 4.3.2, and 5.0.0 through 5.0.2 are affected by a time-of-check-time-of-use flaw in the Git clone base directory (spring.cloud.config.server.git.basedir). The source does not describe the attacker's access requirements or the impact. Upgrade to 4.3.3 or 5.0.3, or later in your line; no fix is listed for versions 3.0.x, 3.1.x, 4.1.x, or 4.2.x.

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
7.4 High 3.1 CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N CNA (vmware)
  • CISA KEV Not listed.
  • EPSS 0.0022, the 12th percentile, on 10 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.