CVE Watchtower

CVE-2026-59381Spring Integration Path Traversal

Spring

Vulnerability Summary

Spring Integration Remote File MGET Local Directory Path Traversal via Server-Controlled Remote Directory. The fix for CVE-2026-40987 validates only the file name against the local directory. For the remote file outbound gateway MGET command, the local directory itself can be derived from the server-controlled listing entry via the documented #remoteDirectory SpEL variable in a local-directory-expression. Since the directory is canonicalized before the containment check, the check passes even though the directory has already escaped the intended root, and the framework then creates the escaped directory. As a result, a malicious FTP, SFTP or SMB server can write files with attacker-controlled content to arbitrary paths outside the configured local directory. Applications are affected if they use the MGET command of an FTP, SFTP or SMB outbound gateway with a local directory expression that references #remoteDirectory (as in the reference documentation examples) and connect to a server that may be malicious or compromised.
Severity Level
HIGH(7.1)
Published Date
Nov 19, 2026
Last Modified
Nov 19, 2026
Exploitation Status
No confirmed exploitation yet
CVE Record Status
Reserved
This CVE ID is referenced in a public advisory, but the CVE Program has not published its official CVE Record yet. Full CVSS/CPE data from NVD will appear here once it does.
Root Weakness (CWE)
The software uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory.
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks.
CVSS v3.1 Base Metrics — Score 7.1 (HIGH)
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:H/A:L
Attack VectorNetwork
Attack ComplexityHigh
Privileges RequiredLow
User InteractionRequired
ScopeChanged
ConfidentialityLow
IntegrityHigh
AvailabilityLow

Affected & Patched Versions

Affected Versions
  • Spring Integration 7.1.0 through 7.1.2
  • Spring Integration 7.0.0 through 7.0.7
  • Spring Integration 6.5.0 through 6.5.11
  • Spring Integration 6.4.0 through 6.4.13
  • Spring Integration 5.5.0 through 5.5.22
Patched Versions
  • Spring Integration 7.1.3 (open source)
  • Spring Integration 7.0.8 (open source)
  • Spring Integration 7.1.2.1 (commercial support only)
  • Spring Integration 7.0.7.1 (commercial support only)
  • Spring Integration 6.5.12 (commercial support only)
  • Spring Integration 6.4.14 (commercial support only)
  • Spring Integration 5.5.23 (commercial support only)

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run Spring Integration and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Nov 19, 2026Published
  • Nov 19, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Spring Integration CVEsYou are reading CVE-2026-59381. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

More Spring Integration CVEs

External References

Data last checked: Nov 20, 2026 05:01 UTC