cve.bz

CVE-2026-40987 vmware spring integration: Path traversal

7.1 highEPSS 0.2%Fix available

High (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.

On this page
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.

Severity

CVSS 3.1

7.1 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:H/A:L
EPSS
0.2% (unchanged from 0.2% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 12th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-06-11. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Spring Integrationfrom 7.0.0 before 7.0.4.1
Spring Integrationfrom 6.5.0 before 6.5.8.1
Spring Integrationfrom 6.4.0 before 6.4.12
Spring Integrationfrom 6.3.0 before 6.3.15
Spring Integrationfrom 5.5.0 before 5.5.21

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-792x-6vq6-j8r9Mavenorg.springframework.integration:spring-integration-file>=7.0.0 <7.0.57.0.5
GHSA-792x-6vq6-j8r9Mavenorg.springframework.integration:spring-integration-file>=6.5.0 <6.5.96.5.9
GHSA-792x-6vq6-j8r9Mavenorg.springframework.integration:spring-integration-file>=6.4.0 <=6.4.11no fix published
GHSA-792x-6vq6-j8r9Mavenorg.springframework.integration:spring-integration-file>=6.3.0 <=6.3.14no fix published
GHSA-792x-6vq6-j8r9Mavenorg.springframework.integration:spring-integration-file<=5.5.20no fix published

Red Hat

Red Hat rates this Important.

Red Hat's statement

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.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Data Grid 8spring-integration-coreNot affected
Red Hat Data Grid 8spring-integration-fileNot affected
Red Hat Data Grid 8spring-integration-sftpNot affected
Red Hat Fuse 7spring-integration-coreWill not fix
Red Hat Fuse 7spring-integration-httpWill not fix
Red Hat JBoss Enterprise Application Platform Expansion Packspring-integration-coreNot affected
Red Hat JBoss Enterprise Application Platform Expansion Packspring-integration-fileNot affected
Red Hat JBoss Enterprise Application Platform Expansion Packspring-integration-sftpNot 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.

GitHub PoC

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.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON