dbcve.org
Spring Cloud ConfigFramework / library · VMware

CVE-2026-40982

CRITICAL · 9.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 →
100/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
Spring Cloud Config allows applications to serve arbitrary text and binary files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead to a directory traversal attack. 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 contains a directory traversal vulnerability in its file-serving functionality. Attackers can craft malicious URLs to access files outside the intended configuration directory, potentially exposing sensitive system files, credentials, or configuration data.

MitigationUpgrade Spring Cloud Config to version 3.1.14+, 4.1.10+, 4.2.7+, 4.3.3+, or 5.0.3+ respectively, depending on the current branch in use.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

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 running service. Check for the spring-cloud-config-server dependency in your project's pom.xml or build.gradle, or identify the running process serving config endpoints.
    Affected if Spring Cloud Config Server is present in the environment
  2. Determine installed Spring Cloud Config Server version
    Run 'java -jar spring-cloud-config-server-*.jar --version' if using the JAR directly, or check the version in your build configuration (pom.xml version of spring-cloud-config-server, or in your dependency management). For deployed instances, check the JAR file name or the /env or /info actuator endpoints if exposed.
    Affected if The version falls within any of these ranges: >= 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, or >= 5.0.0 and < 5.0.3
  3. Test for directory traversal vulnerability (optional verification)
    If authorized, send a request to an endpoint like 'http://config-server-host:port/any-app/any-profile/any-label/..%2F..%2F..%2Fetc%2Fpasswd' or '../..//etc/passwd' and observe if file contents are returned.
    Affected if The server returns contents of files outside the intended config directory

The environment is affected if Spring Cloud Config Server is running with a version within the affected ranges AND file-serving endpoints are accessible without additional access controls preventing the traversal.

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 to version 3.1.14+, 4.1.10+, 4.2.7+, 4.3.3+, or 5.0.3+ respectively, depending on the current branch in use.

Recommended fix High confidence

3.1.14+ (3.x), 4.1.10+ (4.1.x), 4.2.7+ (4.2.x), 4.3.3+ (4.3.x), 5.0.3+ (5.0.x)

  1. Identify the current Spring Cloud Config version in use (check pom.xml, build.gradle, or application dependencies)
  2. For Spring Cloud Config 3.1.x: upgrade to version 3.1.14 or later
  3. For Spring Cloud Config 4.1.x: upgrade to version 4.1.10 or later
  4. For Spring Cloud Config 4.2.x: upgrade to version 4.2.7 or later
  5. For Spring Cloud Config 4.3.x: upgrade to version 4.3.3 or later
  6. For Spring Cloud Config 5.0.x: upgrade to version 5.0.3 or later
  7. Update the version in your project's dependency management file (pom.xml, build.gradle, or equivalent)
  8. Rebuild and redeploy the application with the updated dependency
Caveat Versions 3.1.14, 4.1.10, 4.2.7 require Enterprise Support Only from VMware/Broadcom; 4.3.3 and 5.0.3 appear to be publicly available

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

Fix this in Spring Cloud Config Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
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,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40982 — 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-40982 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