How severe is CVE-2026-40987?

CVE-2026-40987 has a CVSS score of 7.1/10, rated HIGH. Immediate patching is strongly recommended.

How do I fix CVE-2026-40987?

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.

How do I detect CVE-2026-40987 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.integration:spring-integration-file, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-40987 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-40987 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-40987 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-40987?

CVE-2026-40987 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 16th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-40987?

CVE-2026-40987 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-40987 published, and has it been updated?

CVE-2026-40987 was published on June 11, 2026 and was last updated on September 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

HIGH severity

CVE-2026-40987 — spring-integration-file

HIGH

CVE-2026-40987 is a high-severity (CVSS 7.1) Path Traversal vulnerability in org.springframework.integration:spring-integration-file. A fix is available for org.springframework.integration:spring-integration-file — see the affected versions and patch details below.

Remote-file synchronizer in Spring Integration writes server-supplied filename under localDirectory without canonicalization

Also known asGHSA-792x-6vq6-j8r9

Published

Jun 11, 2026

Updated

Sep 20, 2026

Affected

5 pkgs

Patched

2 / 5

Exploits

None indexed

Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-40987.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs16th percentile — riskier than 16% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2026-40987 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

5 pkgs affected

☕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-file

Real-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

5 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.integration:spring-integration-file`	≥ 7.0.0&&< 7.0.5	7.0.5`org.springframework.integration:spring-integration-file:7.0.5`
☕Maven	`org.springframework.integration:spring-integration-file`	≥ 6.5.0&&< 6.5.9	6.5.9`org.springframework.integration:spring-integration-file: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

Affected Products

1 product · 5 configurations

Application

spring integrationvmware

≥ 7.0.0 && < 7.0.4.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.integration:spring-integration-file, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Red Hat ships Spring Integration as a bundled dependency in several middleware products. A flaw was found in Spring Integration's FTP, SFTP, and SMB inbound file synchronization adapters where server-supplied filenames are written to the local filesystem without path canonicalization, allowing a malicious or…

Workaround published by Red Hat

Restrict network access so that applications using Spring Integration file synchronization (FTP, SFTP, SMB inbound adapters) can only connect to trusted, known servers. Use firewall rules or network policies to prevent connections to untrusted endpoints. Additionally, run the application with minimal filesystem permissions to limit the impact of any arbitrary file write.

Source: Red Hat security advisory for CVE-2026-40987 (CC BY 4.0)

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2026-40987 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.1/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

High

Availability

Low

Raw vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:H/A:L

CWE Classification

CWE-22Path Traversal

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Jun 11, 2026

Last updated

Sep 20, 2026

Identifiers

CVE-2026-40987

GHSA-792x-6vq6-j8r9

References

Advisorygithub.com Advisorynvd.nist.gov Webspring.io Packagegithub.com

Related vulnerabilities

This CVE is high severity; 6 of 8 other CVEs with CWE-22 are rated as high or higher (top: critical).

CVE-2026-63445CVE-2026-72697CVE-2026-74907CVE-2026-63225CVE-2026-86071CVE-2026-45140CVE-2026-72695CVE-2026-85731Browse all CWE-22

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 20, 2026