# CVE-2026-40987: Spring Integration File Support: FTP/SFTP/SMB server can write arbitrary files anywhere on the client filesystem > A malicious remote server can write arbitrary files to the client filesystem via path traversal in Spring Integration's file synchronizer, potentially leading to code execution. - **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 11 Jun 2026 - **Updated:** 23 Jun 2026 - **Also known as:** CLSA-2026-1785380362, CLSA-2026-1788470094, CLSA-2026-1791488248, GHSA-792x-6vq6-j8r9, ROOT-APP-MAVEN-CVE-2026-40987 ## What is CVE-2026-40987? CVE-2026-40987 is a high-severity path traversal vulnerability in Spring Integration, published on 11 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description A malicious or compromised FTP/SFTP/SMB server can write arbitrary files anywhere on the client filesystem (outside the configured local-directory) with attacker-controlled content. Affected versions: Spring Integration 7.0.0 through 7.0.4; 6.5.0 through 6.5.8; 6.4.0 through 6.4.11; 6.3.0 through 6.3.14; 5.5.0 through 5.5.20. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-40987? 10 open source packages ship an affected version, including org.springframework.integration:spring-integration-file. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.springframework.integration:spring-integration-file` | Maven | All versions to 5.5.20 | None | | `org.springframework.integration:spring-integration-file` | Maven | All versions to 5.5.20 | None | | `org.springframework.integration:spring-integration-file` | Maven | From 6.3.0 to 6.3.14 | None | | `org.springframework.integration:spring-integration-file` | Maven | From 6.3.0 to 6.3.14 | None | | `org.springframework.integration:spring-integration-file` | Maven | From 6.4.0 to 6.4.11 | None | | `org.springframework.integration:spring-integration-file` | Maven | From 6.4.0 to 6.4.11 | None | | `org.springframework.integration:spring-integration-file` | Maven | From 6.5.0 | 6.5.9 | | `org.springframework.integration:spring-integration-file` | Maven | From 6.5.0 | 6.5.9 | | `org.springframework.integration:spring-integration-file` | Maven | From 7.0.0 | 7.0.5 | | `org.springframework.integration:spring-integration-file` | Maven | From 7.0.0 | 7.0.5 | Products: Vmware Spring Integration. ## How do I fix CVE-2026-40987? Upgrade org.springframework.integration:spring-integration-file to a fixed version for your release line: 6.5.9 or 7.0.5. ## Is CVE-2026-40987 being exploited? There is no known exploitation of CVE-2026-40987 in the wild and no public exploit code. Public exploit code: - CVE-2026-40987 PoC (github_poc): https://github.com/daehyuh/CVE-2026-40987 ## Other vulnerabilities in Spring Integration - [CVE-2026-59324](https://insights.sbomify.com/CVE-2026-59324/): fluxTransform shared RequestMessageHolder causes cross-message header leakage under async fluxFunction (high 8.2) - [CVE-2026-59307](https://insights.sbomify.com/CVE-2026-59307/): Deserialization allow-list silently bypassed: setBeanClassLoader replaces deserializer but mapper keeps stale reference (high 8.0) - [CVE-2026-59311](https://insights.sbomify.com/CVE-2026-59311/): Fixed predictable /tmp/ziptransformer work directory enables symlink pre-creation (medium 6.8) - [CVE-2026-59293](https://insights.sbomify.com/CVE-2026-59293/): SMB minimum protocol dialect defaults to SMB1 (medium 6.6) - [CVE-2026-59274](https://insights.sbomify.com/CVE-2026-59274/): Unbounded decompression in UnZipTransformer enables zip-bomb DoS (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-40987 and fix it if it is affected. What it is: CVE-2026-40987 is a high-severity path traversal vulnerability in Spring Integration, published on 11 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-40987 in the wild and no public exploit code. Affected packages and fixed versions: - org.springframework.integration:spring-integration-file (Maven): affected all versions up to 5.5.20; no fix listed - org.springframework.integration:spring-integration-file (Maven): affected all versions up to 5.5.20; no fix listed - org.springframework.integration:spring-integration-file (Maven): affected from 6.3.0 up to 6.3.14; no fix listed - org.springframework.integration:spring-integration-file (Maven): affected from 6.3.0 up to 6.3.14; no fix listed - org.springframework.integration:spring-integration-file (Maven): affected from 6.4.0 up to 6.4.11; no fix listed - org.springframework.integration:spring-integration-file (Maven): affected from 6.4.0 up to 6.4.11; no fix listed - org.springframework.integration:spring-integration-file (Maven): affected from 6.5.0; fixed in 6.5.9 - org.springframework.integration:spring-integration-file (Maven): affected from 6.5.0; fixed in 6.5.9 - org.springframework.integration:spring-integration-file (Maven): affected from 7.0.0; fixed in 7.0.5 - org.springframework.integration:spring-integration-file (Maven): affected from 7.0.0; fixed in 7.0.5 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-40987/ (Markdown: https://insights.sbomify.com/CVE-2026-40987/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40987 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40987 - OSV: https://osv.dev/vulnerability/CVE-2026-40987 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-40987/ Summaries are generated and may contain mistakes; the official description above is the record.