cve.bz

CVE-2026-41002 vmware spring cloud config

8.1 highEPSS 0.2%Fix available

High (8.1) in vmware spring cloud config. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.cloud:spring-cloud-config-server 4.3.3, 5.0.3.

On this page
The base directory (`spring.cloud.config.server.git.basedir`) used by the Spring Cloud Config Server to clone Git repositories to is susceptible to time-of-check-time-of-use (TOCTOU) attacks. Spring Cloud Config 3.1.x: affected from 3.1.0 through 3.1.13 (inclusive); upgrade to 3.1.14 or greater (Enterprise Support Only). Spring Cloud Config 4.1.x: affected from 4.1.0 through 4.1.9 (inclusive); upgrade to 4.1.10 or greater (Enterprise Support Only). Spring Cloud Config 4.2.x: affected from 4.2.0 through 4.2.6 (inclusive); upgrade to 4.2.7 or greater (Enterprise Support Only). Spring Cloud Config 4.3.x: affected from 4.3.0 through 4.3.2 (inclusive); upgrade to 4.3.3 or greater. Spring Cloud Config 5.0.x: affected from 5.0.0 through 5.0.2 (inclusive); upgrade to 5.0.3 or greater.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-05-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-41002 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-41002?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-41002?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-41002 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-41002

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-41002](https://cve.bz/cve/badge/CVE-2026-41002.svg)](https://cve.bz/cve/CVE-2026-41002)

HTML:

<a href="https://cve.bz/cve/CVE-2026-41002"><img src="https://cve.bz/cve/badge/CVE-2026-41002.svg" alt="CVE-2026-41002"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring Cloud Configfrom 3.1.0 before 3.1.14
Spring Cloud Configfrom 4.1.0 before 4.1.10
Spring Cloud Configfrom 4.2.0 before 4.2.7
Spring Cloud Configfrom 4.3.0 before 4.3.3
Spring Cloud Configfrom 5.0.0 before 5.0.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-86wq-234q-r6wgMavenorg.springframework.cloud:spring-cloud-config-server>=3.1.0 <=3.1.13no fix published
GHSA-86wq-234q-r6wgMavenorg.springframework.cloud:spring-cloud-config-server>=4.1.0 <=4.1.9no fix published
GHSA-86wq-234q-r6wgMavenorg.springframework.cloud:spring-cloud-config-server>=4.2.0 <=4.2.6no fix published
GHSA-86wq-234q-r6wgMavenorg.springframework.cloud:spring-cloud-config-server>=4.3.0 <4.3.34.3.3
GHSA-86wq-234q-r6wgMavenorg.springframework.cloud:spring-cloud-config-server>=5.0.0 <5.0.35.0.3
GHSA-86wq-234q-r6wgMavenorg.springframework.cloud:spring-cloud-config-server>=3.0.0 <=3.0.7no fix published

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON