CVE-2026-22739 is a high-severity (CVSS 8.6) Path Traversal vulnerability in org.springframework.cloud:spring-cloud-config-server. A fix is available for org.springframework.cloud:spring-cloud-config-server — see the affected versions and patch details below.
Spring Cloud Config Profile Substitution Can Allow Unintended Access To Files And Enable SSRF Attacks
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-22739.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2026-22739 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.cloud:spring-cloud-config-server | ≥ 4.3.0&&< 4.3.2 | 4.3.2org.springframework.cloud:spring-cloud-config-server:4.3.2 |
| ☕Maven | org.springframework.cloud:spring-cloud-config-server | ≥ 5.0.0-M1&&< 5.0.2 | 5.0.2org.springframework.cloud:spring-cloud-config-server:5.0.2 |
| ☕Maven | org.springframework.cloud:spring-cloud-config-server | ≥ 4.2.0 | No fix |
| ☕Maven | org.springframework.cloud:spring-cloud-config-server | ≥ 4.0.0 | No fix |
| ☕Maven | org.springframework.cloud:spring-cloud-config-server | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.cloud:spring-cloud-config-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.cloud:spring-cloud-config-server to 4.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-22739 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-22739 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2026-22739. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
How to detect CVE-2026-22739
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id cve-2026-22739 -u https://target- Template
- Spring Cloud Config Server - Path Traversal
- Severity
- high
- Impact
- Attackers can access arbitrary files outside intended directories, potentially exposing sensitive information
- Remediation
- "Upgrade to versions 3.1.13, 4.1.9, 4.2.3, 4.3.2, or 5.0.2 or later.
Template by ProjectDiscovery nuclei-templates (0x_Akoko, vulnh0lic), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is CVE-2026-22739 in your dependencies?
O3 Security finds CVE-2026-22739 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.