CVE-2026-41002: The base directory (`spring.cloud.config.server.git.basedir`) used by the Spring Cloud Config Server to clone

Routine

HIGH 7.2UPGRADE

CVE-2026-41002 is a high-severity flaw (CVSS 7.2) affecting spring cloud config. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Local
Attack complexity	High
Privileges needed	High
User interaction	None
EPSS exploit chance	0.2% (top 88%)
CISA exploited list	No
Weakness	CWE-367
Published	2026-05-07
Last modified	2026-10-26

Publisher (CNA): VMware · Vendor: vmware

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-07 04:16 UTCPublished CVE record published
2026-10-26 19:10 UTCUpdated Record last modified

vmware spring cloud config UPGRADE

Affected: >= 3.1.0 and < 3.1.14 · >= 4.1.0 and < 4.1.10 · >= 4.2.0 and < 4.2.7 · >= 4.3.0 and < 4.3.3 · >= 5.0.0 and < 5.0.3

Fixed in: 3.1.14, 4.1.10, 4.2.7, 4.3.3, 5.0.3

Safe to downgrade to: a release before 3.1.0

1. Check installed version

apt-cache policy spring-cloud-config || rpm -q spring-cloud-config || spring-cloud-config --version

2. UPGRADE to 3.1.14 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade spring-cloud-config

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade spring-cloud-config

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 3.1.0 (Debian / Ubuntu)

apt-cache madison spring-cloud-config sudo apt install spring-cloud-config=<VERSION_BEFORE_3.1.0> sudo apt-mark hold spring-cloud-config

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list spring-cloud-config sudo dnf downgrade spring-cloud-config-<VERSION_BEFORE_3.1.0> sudo dnf versionlock add spring-cloud-config

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-41002?

spring cloud config: upgrade to 3.1.14, 4.1.10, 4.2.7, 4.3.3, 5.0.3. Exact commands for each OS are on this page.

Is CVE-2026-41002 being exploited?

CVE-2026-41002 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-41002 affect?

CVE-2026-41002 affects spring cloud config. Severity is high (CVSS 7.2). 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 t

How urgent is CVE-2026-41002?

Priority 28/100. High severity

Software pages

VMware vulnerabilities · Git vulnerabilities

Related CVEs

CVE-2026-40982 CRITICAL 9.1 UPGRADE Spring Cloud Config allows applications to serve arbitrary text and binary files through the spring-cloud-conf
CVE-2026-40981 HIGH 7.5 UPGRADE When using Google Secrets Manager as a backend for the Spring Cloud Config server a client can craft a request
CVE-2026-41004 MEDIUM 4.4 UPGRADE When enabling trace logging in Spring Cloud Config Server sensitive information was placed in plain text in th
CVE-2026-47836 HIGH 7.2 UPGRADE The base directory (spring.cloud.config.server.svn.basedir) used by the Spring Cloud Config Server to clone SV
CVE-2026-47837 MEDIUM 6.8 UPGRADE Missing Authentication for Critical Function vulnerability in Spring Spring Cloud Config allows Webhook reques

References

← Back to latest CVEs