dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-40987

HIGH · 7.1 CVSS v3.1 Published 2026-06-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
75/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a path traversal vulnerability in Spring Integration's FTP/SFTP/SMB client components. When a client connects to a malicious or compromised server, the server can send directory traversal sequences (e.g., '../') in filenames, allowing arbitrary file writes outside the configured local directory with attacker-controlled content.

MitigationUpgrade Spring Integration to a patched version once available, and ensure strict path validation is enforced to prevent directory traversal in file operations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
High
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring Integration version
    Check your project's build file (pom.xml, build.gradle) for the spring-integration-core version, or inspect the JAR manifest in your deployed application
    Affected if The version is before 5.5.21, 6.3.15, 6.4.12, 6.5.9, or 7.0.5 (vulnerable ranges)
  2. Confirm FTP client usage
    Search project configuration and code for FTP outbound channel adapters or gateways: look for bean definitions with class names containing FtpOutbound or references to namespace 'int-ftp' in XML configs
    Affected if FTP outbound adapters or gateways are defined and Spring Integration version is vulnerable
  3. Confirm SFTP client usage
    Search project configuration and code for SFTP outbound channel adapters or gateways: look for bean definitions with class names containing SftpOutbound or references to namespace 'int-sftp' in XML configs
    Affected if SFTP outbound adapters or gateways are defined and Spring Integration version is vulnerable
  4. Confirm SMB client usage
    Search project configuration and code for SMB (SMB/CIFS) outbound channel adapters or gateways: look for bean definitions with class names containing SmbOutbound or references to namespace 'int-smb' in XML configs
    Affected if SMB outbound adapters or gateways are defined and Spring Integration version is vulnerable

You are affected if you use Spring Integration with vulnerable versions (before 5.5.21, 6.3.15, 6.4.12, 6.5.9, or 7.0.5) AND have FTP, SFTP, or SMB outbound adapters/gateways configured to connect to potentially untrusted servers

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Spring Integration to a patched version once available, and ensure strict path validation is enforced to prevent directory traversal in file operations.

Recommended fix Moderate confidence

Spring Integration 5.5.21, 6.3.15, 6.4.12, 6.5.9, or 7.0.5 (depending on your current branch)

  1. 1. Identify the currently deployed Spring Integration version from your project dependencies (e.g., pom.xml, build.gradle)
  2. 2. Determine which version branch your current deployment uses (5.5.x, 6.3.x, 6.4.x, 6.5.x, or 7.0.x)
  3. 3. For Spring Integration 5.5.x: upgrade to version 5.5.21 or later
  4. 4. For Spring Integration 6.3.x: upgrade to version 6.3.15 or later
  5. 5. For Spring Integration 6.4.x: upgrade to version 6.4.12 or later
  6. 6. For Spring Integration 6.5.x: upgrade to version 6.5.9 or later
  7. 7. For Spring Integration 7.0.x: upgrade to version 7.0.5 or later
  8. 8. Update the version in your build configuration file (pom.xml or build.gradle)
Caveat Spring patch releases typically contain bug fixes and security patches with minimal breaking changes; review the release notes for your target version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40987 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40987 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data