NVD / CVE Program· CNA vmware

CVE-2026-22739: Spring Cloud Config Profile Substitution Can Allow Unintended Access To Files And Enable SSRF Attacks

Noroxi assessment

Priority: Monitor (action score 34/100)

A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
Public proof-of-concept code exists (Exploit-DB / GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 69.5% of all records.
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.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: org.springframework.cloud:spring-cloud-config-server (Maven) 4.3.2, 5.0.2.

Low priority for now. Upgrade to org.springframework.cloud:spring-cloud-config-server (Maven) 4.3.2, 5.0.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Vulnerability in Spring Cloud when substituting the profile parameter from a request made to the Spring Cloud Config Server configured to the native file system as a backend, because it was possible to access files outside of the configured search directories.This issue affects Spring Cloud: from 3.1.X before 3.1.13, from 4.1.X before 4.1.9, from 4.2.X before 4.2.3, from 4.3.X before 4.3.2, from 5.0.X before 5.0.2.

HighCVSS 8.6 · v3.1—Proof of concept Fix available

Published: Mar 23, 2026
Updated: Sep 4, 2026
EPSS: 1.2% · 69th percentile
CWE: CWE-22

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 34 / 40 · 8.6 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 1.2%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · vmware: 8.6; 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.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
vmware	spring cloud config	cpe:2.3:a:vmware:spring_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 configbefore 3.1.13
vmware spring cloud config4.1.0 and later · before 4.1.9
vmware spring cloud config4.2.0 and later · before 4.2.6
vmware spring cloud config4.3.0 and later · before 4.3.2
vmware spring cloud config5.0.0 and later · before 5.0.2

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
- 3.1.x and later · before 3.1.13affected
- 4.1.x and later · before 4.1.9affected
- 4.2.x and later · before 4.2.3affected
- 4.3.x and later · before 4.3.2affected
- 5.0.x and later · before 5.0.2affected

Package-level exposure

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

Ecosystem	Package	Affected range	Fix
Maven	org.springframework.cloud:spring-cloud-config-server	from 4.0.0 · up to and including 4.1.7	—
Maven	org.springframework.cloud:spring-cloud-config-server	from 4.2.0 · up to and including 4.2.4	—
Maven	org.springframework.cloud:spring-cloud-config-server	from 4.3.0 · before 4.3.2	4.3.2
Maven	org.springframework.cloud:spring-cloud-config-server	from 5.0.0-M1 · before 5.0.2	5.0.2
Maven	org.springframework.cloud:spring-cloud-config-server	up to and including 3.1.10	—

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
60This week
CVE-2020-5405Directory Traversal with spring-cloud-config-server
47Plan

Published before and after this one in the same product

← EarlierCVE-2023-20859Mar 23, 2023 · In Spring Vault, versions 3.0.x prior to 3.0.2 and versions 2.3.x prior to 2.3.3 and older versions, an application is vulnerable to…
22Monitor
Later →CVE-2026-40981May 7, 2026 · When using Google Secrets Manager as a backend for the Spring Cloud Config server a client can craft a request to the config server…
30Monitor
Later →CVE-2026-40982May 7, 2026 · Spring Cloud Config allows applications to serve arbitrary text and binary files through the spring-cloud-config-server module.
36Monitor

Remediation

Which version to upgrade to

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

Product / package	Fixed version	Source
Maven:org.springframework.cloud:spring-cloud-config-server	4.3.2	Package registry (OSV)
Maven:org.springframework.cloud:spring-cloud-config-server	5.0.2	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Nuclei detection template ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Nuclei detection template	Nuclei template CVE-2026-22739	—

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.

No history yet (it accumulates with the daily EPSS job).

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.

CVE-2026-4098245 days apartSpring Cloud Config allows applications to serve arbitrary text and binary files through the spring-cloud-config-server module.
36Monitor
CVE-2026-47894157 days apartSpring Cloud Config Server Native Environment Repository Exposure
30Monitor

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: low · data or configuration can be modified
Availability: low · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: Low
Availability impact: Low

Weakness class (CWE)

CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVSS vector

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

nvd-secondary

Root cause

A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.

The bug in code

The whole CWE-22 class

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

Vulnerable

1const file = path.join(ROOT, req.query.name);
2res.sendFile(file);

Fixed

1const file = path.resolve(ROOT, req.query.name);
2if (!file.startsWith(ROOT + path.sep)) {
3  return res.sendStatus(400);
4}
5res.sendFile(file);

Attack context

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

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 28, 2026, 10:48 PM UTC

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

References

spring.io/security/cve-2026-22739

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

All records