# CVE-2026-22739: Spring Cloud Config Profile Substitution Can Allow Unintended Access To Files And Enable SSRF Attacks > Attackers can access files outside configured directories and perform SSRF attacks when Spring Cloud Config Server uses native file system backend. - **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 Mar 2026 - **Updated:** 24 Mar 2026 - **Also known as:** GHSA-3qwq-q9vm-5j42, ROOT-APP-MAVEN-CVE-2026-22739 ## What is CVE-2026-22739? CVE-2026-22739 is a high-severity path traversal vulnerability in Spring Cloud, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-22739? 10 open source packages ship an affected version, including org.springframework.cloud:spring-cloud-config-server. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.cloud:spring-cloud-config-server` | Maven | All versions to 3.1.10 | None | | `org.springframework.cloud:spring-cloud-config-server` | Maven | All versions to 3.1.10 | None | | `org.springframework.cloud:spring-cloud-config-server` | Maven | From 4.0.0 to 4.1.7 | None | | `org.springframework.cloud:spring-cloud-config-server` | Maven | From 4.0.0 to 4.1.7 | None | | `org.springframework.cloud:spring-cloud-config-server` | Maven | From 4.2.0 to 4.2.4 | None | | `org.springframework.cloud:spring-cloud-config-server` | Maven | From 4.2.0 to 4.2.4 | None | | `org.springframework.cloud:spring-cloud-config-server` | Maven | From 4.3.0 | 4.3.2 | | `org.springframework.cloud:spring-cloud-config-server` | Maven | From 4.3.0 | 4.3.2 | | `org.springframework.cloud:spring-cloud-config-server` | Maven | From 5.0.0-M1 | 5.0.2 | | `org.springframework.cloud:spring-cloud-config-server` | Maven | From 5.0.0-M1 | 5.0.2 | Products: Vmware Spring Cloud Config. ## How do I fix CVE-2026-22739? Upgrade org.springframework.cloud:spring-cloud-config-server to a fixed version for your release line: 4.3.2 or 5.0.2. ## Is CVE-2026-22739 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22739 exists. Public exploit code: - Spring Cloud Config Server - Path Traversal (nuclei): http/cves/2026/CVE-2026-22739.yaml ## Other vulnerabilities in Spring Cloud - [CVE-2020-5410](https://insights.sbomify.com/CVE-2020-5410/): VMware Tanzu Spring Cloud Config Directory Traversal (high 7.5, exploited in the wild) - [CVE-2026-40982](https://insights.sbomify.com/CVE-2026-40982/): Spring Cloud Config vulnerable to Path Traversal (critical 9.1) - [CVE-2026-40981](https://insights.sbomify.com/CVE-2026-40981/): Spring Cloud Config has an Authorization Bypass Through User-Controlled Key (high 7.5) - [CVE-2026-41002](https://insights.sbomify.com/CVE-2026-41002/): Spring Cloud Config Server Susceptible To TOCTOU Attack (high 7.4) - [CVE-2026-47836](https://insights.sbomify.com/CVE-2026-47836/): Spring Cloud Config Server Susceptible To TOCTOU Attack When Using SVN (high 7.2) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-22739 and fix it if it is affected. What it is: CVE-2026-22739 is a high-severity path traversal vulnerability in Spring Cloud, published on 24 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22739 exists. Affected packages and fixed versions: - org.springframework.cloud:spring-cloud-config-server (Maven): affected all versions up to 3.1.10; no fix listed - org.springframework.cloud:spring-cloud-config-server (Maven): affected all versions up to 3.1.10; no fix listed - org.springframework.cloud:spring-cloud-config-server (Maven): affected from 4.0.0 up to 4.1.7; no fix listed - org.springframework.cloud:spring-cloud-config-server (Maven): affected from 4.0.0 up to 4.1.7; no fix listed - org.springframework.cloud:spring-cloud-config-server (Maven): affected from 4.2.0 up to 4.2.4; no fix listed - org.springframework.cloud:spring-cloud-config-server (Maven): affected from 4.2.0 up to 4.2.4; no fix listed - org.springframework.cloud:spring-cloud-config-server (Maven): affected from 4.3.0; fixed in 4.3.2 - org.springframework.cloud:spring-cloud-config-server (Maven): affected from 4.3.0; fixed in 4.3.2 - org.springframework.cloud:spring-cloud-config-server (Maven): affected from 5.0.0-M1; fixed in 5.0.2 - org.springframework.cloud:spring-cloud-config-server (Maven): affected from 5.0.0-M1; fixed in 5.0.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-22739/ (Markdown: https://insights.sbomify.com/CVE-2026-22739/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22739 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22739 - OSV: https://osv.dev/vulnerability/CVE-2026-22739 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-22739/ Summaries are generated and may contain mistakes; the official description above is the record.