Skip to content
Noroxi
CVE-2026-40981· NVD / CVE Program· CNA vmware

When using Google Secrets Manager as a backend for the Spring Cloud Config server a client can craft a request to the config server potentia

When using Google Secrets Manager as a backend for the Spring Cloud Config server a client can craft a request to the config server potentially exposing secrets from unintended GCP projects. 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.

HighCVSS 7.5 · v3.1—No exploit Fix available

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
May 7, 2026
Updated
Jul 15, 2026
EPSS
0.5% · 39th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · vmware
7.5
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
vmwarespring cloud config

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • vmware spring cloud config3.1.0 and later · before 3.1.14
  • vmware spring cloud config4.1.0 and later · before 4.1.10
  • vmware spring cloud config4.2.0 and later · before 4.2.7
  • vmware spring cloud config4.3.0 and later · before 4.3.3
  • vmware spring cloud config5.0.0 and later · before 5.0.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (vmware). Independent of NVD's CPE analysis and usually ahead of it.

  • Spring Spring Cloud Config

    • 3.1.0 and later · before 3.1.14affected
    • 4.1.0 and later · before 4.1.10affected
    • 4.2.0 and later · before 4.2.7affected
    • 4.3.0 and later · before 4.3.3affected
    • 5.0.0 and later · before 5.0.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.springframework.cloud:spring-cloud-config-serverfrom 3.1.0 · up to and including 3.1.13—
Mavenorg.springframework.cloud:spring-cloud-config-serverfrom 4.1.0 · up to and including 4.1.9—
Mavenorg.springframework.cloud:spring-cloud-config-serverfrom 4.2.0 · up to and including 4.2.6—
Mavenorg.springframework.cloud:spring-cloud-config-serverfrom 4.3.0 · before 4.3.34.3.3
Mavenorg.springframework.cloud:spring-cloud-config-serverfrom 5.0.0 · before 5.0.35.0.3

Same product

vmware: all records

Other highest-scoring records for the same primary product.

  • CVE-2020-5410Directory Traversal with spring-cloud-config-serverKEV
    89Now
  • CVE-2019-3799Directory Traversal with spring-cloud-config-server
    52Plan
  • CVE-2020-5405Directory Traversal with spring-cloud-config-server
    47Plan
  • CVE-2026-47837Spring Cloud Config Server Monitor Endpoint Does Not Validate Webhook Requests
    39Monitor
  • CVE-2026-40982Spring Cloud Config allows applications to serve arbitrary text and binary files through the spring-cloud-config-server module.
    36Monitor
  • CVE-2026-22739Spring Cloud Config Profile Substitution Can Allow Unintended Access To Files And Enable SSRF Attacks
    34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.springframework.cloud:spring-cloud-config-server4.3.3Package registry (OSV)
Maven:org.springframework.cloud:spring-cloud-config-server5.0.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-639 · Authorization Bypass Through User-Controlled Key

CVSS vector

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

nvd-secondary

Root cause

The endpoint fetches the record by the ID sent in the request, but never checks whether the record belongs to the requesting user.

The bug in code

The whole CWE-639 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
const invoice = await Invoice.findById(req.params.id);res.json(invoice);

Fixed

ts
const invoice = await Invoice.findOne({  id: req.params.id,  ownerId: req.user.id,});if (!invoice) return res.sendStatus(404);res.json(invoice);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records