Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

GHSA-792x-6vq6-j8r9 — spring-integration-file

HIGH

GHSA-792x-6vq6-j8r9 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.

Spring Integration File Support: FTP/SFTP/SMB server can write arbitrary files anywhere on the client filesystem

Also known asCVE-2026-40987
Published
Jun 11, 2026
Updated
Aug 7, 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 GHSA-792x-6vq6-j8r9.

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

GHSA-792x-6vq6-j8r9 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
EcosystemPackageVulnerable rangeFix
☕Mavenorg.springframework.integration:spring-integration-file≥ 7.0.0&&< 7.0.57.0.5org.springframework.integration:spring-integration-file:7.0.5
☕Mavenorg.springframework.integration:spring-integration-file≥ 6.5.0&&< 6.5.96.5.9org.springframework.integration:spring-integration-file:6.5.9
☕Mavenorg.springframework.integration:spring-integration-file≥ 6.4.0No fix
☕Mavenorg.springframework.integration:spring-integration-file≥ 6.3.0No fix
☕Mavenorg.springframework.integration:spring-integration-fileall versionsNo fix

Affected Products

1 product · 5 configurations
Application
spring integrationvmware
≥ 7.0.0 && < 7.0.4.1
range

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. 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 GHSA-792x-6vq6-j8r9 is resolved across your whole dependency graph.

  3. 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 GHSA-792x-6vq6-j8r9 (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 GHSA-792x-6vq6-j8r9 in your dependencies?

Find it across Maven, including transitive dependencies.

GHSA-792x-6vq6-j8r9: spring-integration-file | O3 Security