8.6High
Vmware Spring Cloud Config
CVE-2026-22739
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.
What this means for your business
- It affects Vmware Spring Cloud Config. It matters if your company, or a supplier that handles your data, runs it.
- An attacker can use it remotely, over a network, without a login, and without anyone at your company clicking anything.
- FIRST's prediction model gives it a 1% chance of attack attempts being seen in the next 30 days, ranking above 66% of all known flaws.
What to do
- 1Check whether your company or your suppliers run Vmware Spring Cloud Config, and which version. The affected versions are listed further down this page.
- 2If you do, apply the vendor's fix. A patch or vendor advisory has been published.
Not sure if your company is exposed?
Fastnexa’s certified penetration testers can check whether attackers could use this flaw, or others like it, against your websites, apps and network. The full test is free for our first 10 founding clients until 31 December 2026.
Scoring
- CVSS
- 8.6 (v3.1)
- Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L- Weakness
- CWE-22
- Assigned by
- security@vmware.com
Dates
- Published
- 2026-03-24
- Last modified
- 2026-09-04
- Sources
- NVD
Affected products
- Vmware Spring Cloud Config- 3.1.13, 4.1.0 - 4.1.9, 4.2.0 - 4.2.6, 4.3.0 - 4.3.2, 5.0.0 - 5.0.2
As listed in the NVD configuration data. Not a statement about your estate.