dbcve.org
Spring Cloud ConfigFramework / library · VMware

CVE-2026-41002

HIGH · 8.1 CVSS v3.1 Published 2026-05-07
Fix available
A fix is available. Upgrade to 3.1.14 / 4.1.10 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Spring Cloud Config Server's git-basedir configuration is vulnerable to TOCTOU attacks, where an attacker can manipulate the directory used for cloning Git repositories between the time it is checked and the time it is used, potentially allowing arbitrary file write or manipulation during the git clone operation.

MitigationUpgrade Spring Cloud Config Server to version 3.1.14+, 4.1.10+, 4.2.7+, 4.3.3+, or 5.0.3+ (or later) as appropriate for your release line. Test thoroughly in a non-production environment before deploying.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring Cloud ConfigFramework / library
Affected:>= 3.1.0, < 3.1.14>= 4.1.0, < 4.1.10>= 4.2.0, < 4.2.7>= 4.3.0, < 4.3.3>= 5.0.0, < 5.0.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring Cloud Config Server installation
    Locate the Spring Cloud Config Server JAR file or check the application's pom.xml for spring-cloud-config-server dependency and note the version number
    Affected if The installed version falls within any of these ranges: 3.1.0 to 3.1.13, 4.1.0 to 4.1.9, 4.2.0 to 4.2.6, 4.3.0 to 4.3.2, or 5.0.0 to 5.0.2
  2. Verify git backend is enabled
    Examine the application configuration (application.yml or application.properties) for the property spring.cloud.config.server.git.uri to confirm a Git repository backend is configured
    Affected if spring.cloud.config.server.git.uri is set to a Git repository URL, enabling the git backend
  3. Check for basedir configuration
    Search configuration files for spring.cloud.config.server.git.base-dir or spring.cloud.config.server.git.basedir properties and note the configured directory path
    Affected if The base-dir or basedir property is explicitly set in the configuration
  4. Inspect runtime environment
    At runtime, examine the process environment or configuration properties for spring.cloud.config.server.git.* settings to see if basedir is in use
    Affected if The git-basedir or basedir configuration is actively in use when the application runs

You are affected if the installed Spring Cloud Config Server version is within the vulnerable ranges AND the git backend is enabled with a basedir configuration present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1.14 / 4.1.10 / 4.2.7 or later
Fixed in 3.1.144.1.104.2.7
Interim mitigation

Upgrade Spring Cloud Config Server to version 3.1.14+, 4.1.10+, 4.2.7+, 4.3.3+, or 5.0.3+ (or later) as appropriate for your release line. Test thoroughly in a non-production environment before deploying.

Recommended fix High confidence

4.3.3 (or 5.0.3 if upgrading to 5.x branch)

  1. 1. Identify the current Spring Cloud Config Server version in use by checking your project's dependency management (e.g., pom.xml, build.gradle)
  2. 2. Determine which branch (3.1.x, 4.1.x, 4.2.x, 4.3.x, or 5.0.x) your current version belongs to
  3. 3. For 4.3.x branch: upgrade to version 4.3.3 or later by updating the spring-cloud-config-server version in your dependency management
  4. 4. For 5.0.x branch: upgrade to version 5.0.3 or later
  5. 5. For 3.1.x, 4.1.x, or 4.2.x branches: note these require Enterprise Support; consider upgrading to a newer branch (4.3.x or 5.0.x) which has publicly available fixes
  6. 6. After upgrading, verify the application starts successfully and git-based configuration repositories function correctly
  7. 7. Test the spring.cloud.config.server.git.basedir functionality to confirm the TOCTOU vulnerability is resolved
Caveat Upgrading across major version branches (e.g., 3.x to 4.x, 4.x to 5.x) may introduce breaking changes; review Spring Cloud Config release notes for migration guidance

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Cloud Config Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,576.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41002 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-41002 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data