CVE-2026-40987
HIGHCVE-2026-40987 is a high-severity (CVSS 7.1) Path Traversal vulnerability in org.springframework.integration:spring-integration-file. O3 Security confirms whether CVE-2026-40987 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Spring Integration File Support: FTP/SFTP/SMB server can write arbitrary files anywhere on the client filesystem
Real-World Exposure
org.springframework.integration:spring-integration-file☕org.springframework.integration:spring-integration-file☕org.springframework.integration:spring-integration-file☕org.springframework.integration:spring-integration-file☕org.springframework.integration:spring-integration-fileReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.integration:spring-integration-file | ≥ 7.0.0&&< 7.0.5 | 7.0.5 |
| ☕Maven | org.springframework.integration:spring-integration-file | ≥ 6.5.0&&< 6.5.9 | 6.5.9 |
| ☕Maven | org.springframework.integration:spring-integration-file | ≥ 6.4.0 | No fix |
| ☕Maven | org.springframework.integration:spring-integration-file | ≥ 6.3.0 | No fix |
| ☕Maven | org.springframework.integration:spring-integration-file | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.integration:spring-integration-file. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.springframework.integration:spring-integration-file to 7.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-40987 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-40987 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-40987. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-40987 in your dependencies?
O3 detects CVE-2026-40987 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.