CVE-2026-22739
Directory Traversal in Spring Cloud Config Server Enables Unauthorized File Access
Publication date: 2026-03-24
Last updated on: 2026-03-24
Assigner: VMware
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| vmware | spring_cloud | From 3.1.0 (inc) to 3.1.13 (exc) |
| vmware | spring_cloud | From 4.1.0 (inc) to 4.1.9 (exc) |
| vmware | spring_cloud | From 4.2.0 (inc) to 4.2.3 (exc) |
| vmware | spring_cloud | From 4.3.0 (inc) to 4.3.2 (exc) |
| vmware | spring_cloud | From 5.0.0 (inc) to 5.0.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-22739 is a vulnerability in Spring Cloud Config Server that occurs when the profile parameter from a request is substituted. If the server is configured to use the native file system as a backend, this substitution can allow unauthorized access to files outside the intended search directories.
Additionally, when the server uses a source control backend, the profile parameter can be injected into the URL pointing to the source control repository, which can enable Server-Side Request Forgery (SSRF) attacks.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to sensitive files outside the configured directories on the Spring Cloud Config Server, potentially exposing confidential information.
In cases where a source control backend is used, it can also enable SSRF attacks, which might allow attackers to make unauthorized requests from the server, potentially leading to further exploitation or data breaches.
The CVSS base score of 8.6 indicates a high severity impact, with high confidentiality impact, low integrity impact, and low availability impact.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate the vulnerability in Spring Cloud Config Server, you should upgrade to the fixed versions provided by the vendor.
- Upgrade to version 3.1.13 (Enterprise Support only)
- Upgrade to version 4.1.9 (Enterprise Support only)
- Upgrade to version 4.2.6 (Enterprise Support only)
- Upgrade to version 4.3.2 (Open Source Software)
- Upgrade to version 5.0.2 (Open Source Software)