CVSS 3.1
7.1 highCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:H/A:LHigh (7.1) in vmware spring integration. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.integration:spring-integration-file 6.5.9, 7.0.5.
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:H/A:Lorg.springframework.integration:spring-integration-file (Maven): fixed in 7.0.5, 6.5.9Explain CVE-2026-40987 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40987?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40987?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-40987 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Spring Integration | from 7.0.0 before 7.0.4.1 |
| Spring Integration | from 6.5.0 before 6.5.8.1 |
| Spring Integration | from 6.4.0 before 6.4.12 |
| Spring Integration | from 6.3.0 before 6.3.15 |
| Spring Integration | from 5.5.0 before 5.5.21 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-792x-6vq6-j8r9 | Maven | org.springframework.integration:spring-integration-file | >=7.0.0 <7.0.5 | 7.0.5 |
| GHSA-792x-6vq6-j8r9 | Maven | org.springframework.integration:spring-integration-file | >=6.5.0 <6.5.9 | 6.5.9 |
| GHSA-792x-6vq6-j8r9 | Maven | org.springframework.integration:spring-integration-file | >=6.4.0 <=6.4.11 | no fix published |
| GHSA-792x-6vq6-j8r9 | Maven | org.springframework.integration:spring-integration-file | >=6.3.0 <=6.3.14 | no fix published |
| GHSA-792x-6vq6-j8r9 | Maven | org.springframework.integration:spring-integration-file | <=5.5.20 | no fix published |
Red Hat rates this Important.
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 compromised remote server to write arbitrary files outside the configured local directory. Products shipping spring-integration-file, spring-integration-sftp, or spring-integration-ftp modules are directly exposed. Products bundling only spring-integration-core may not have the vulnerable code path but are included pending detailed analysis.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Data Grid 8 | spring-integration-core | Not affected | |
| Red Hat Data Grid 8 | spring-integration-file | Not affected | |
| Red Hat Data Grid 8 | spring-integration-sftp | Not affected | |
| Red Hat Fuse 7 | spring-integration-core | Will not fix | |
| Red Hat Fuse 7 | spring-integration-http | Will not fix | |
| Red Hat JBoss Enterprise Application Platform Expansion Pack | spring-integration-core | Not affected | |
| Red Hat JBoss Enterprise Application Platform Expansion Pack | spring-integration-file | Not affected | |
| Red Hat JBoss Enterprise Application Platform Expansion Pack | spring-integration-sftp | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-40987.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.