CVE-2026-22739
No exploitation reported by the sources we read.
- Published2026-03-24
- Fixed in5.0.2 · 4.3.2 · 4.2.6 · 4.1.9 · 3.1.13
- WeaknessCWE-22
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
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.
Timeline
dates in UTC- 2026-03-2401:17CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-22739?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-22739?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 5.0 | ≥ 5.0.0, < 5.0.2 | 5.0.2 | NVD |
| 4.3 | ≥ 4.3.0, < 4.3.2 | 4.3.2 | NVD |
| 4.2 | ≥ 4.2.0, < 4.2.6 | 4.2.6 | NVD |
| 4.1 | ≥ 4.1.0, < 4.1.9 | 4.1.9 | NVD |
| 3.1 | < 3.1.13 | 3.1.13 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Vmware spring cloud config to 5.0.2 · 4.3.2 · 4.2.6 · 4.1.9 · 3.1.13
Advisories and patches
- spring.ioVendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
- Published
- 2026-03-24
- Last Modified
- 2026-09-04
- NVD status
- Undergoing Analysis
Frequently asked questions
What is CVE-2026-22739?
Is CVE-2026-22739 actively exploited?
What is the CVSS score for CVE-2026-22739?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.