Categories
CVE-2026-40987 high CVSS 7.1

Path Traversal in org.springframework.integration:spring-integration-file (CVE-2026-40987)

Summary

Path traversal in org.springframework.integration:spring-integration-file (CVE-2026-40987). Data can be tampered with by attackers.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-40987 has been found in org.springframework.integration:spring-integration-file.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "org.springframework.integration:spring-integration-file CVE-2026-40987" on the vendor's site.

CVE-2026-40987 (org.springframework.integration:spring-integration-file) — CWE-22 / CVSS v3 7.1
Attack vector: remote (network-reachable)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Path traversal (CWE-22) exists in org.springframework.integration:spring-integration-file.

📍 Affected scope

Check the vendor advisory for the affected versions of org.springframework.integration:spring-integration-file.

🔥 Severity

Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.springframework.integration:spring-integration-file を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

maven org.springframework.integration:spring-integration-file
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"5.5.20"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details