# CVE-2026-59293: SMB minimum protocol dialect defaults to SMB1

> Spring Integration defaults to insecure SMB1, allowing attackers to bypass signing and encryption via NTLM relay or MITM attacks.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-5v9f-jcmr-jg2q

## What is CVE-2026-59293?

CVE-2026-59293 is a medium-severity vulnerability in Spring Integration, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Unless the application explicitly raises smbMinVersion, the jCIFS client will negotiate down to SMB1/CIFS, which lacks mandatory signing/encryption and is vulnerable to NTLM relay and content-tampering MITM.
Spring Integration 7.1.0
Spring Integration 7.0.0 - 7.0.5
Spring Integration 6.5.0 - 6.5.10
Spring Integration 6.4.0 - 6.4.12

Weakness: CWE-757 (Selection of Less-Secure Algorithm During Negotiation)

## Which versions are affected by CVE-2026-59293?

It affects 1 product.


Products: Vmware Spring Integration.

## How do I fix CVE-2026-59293?

Upgrade to a fixed version.

## Is CVE-2026-59293 being exploited?

There is no known exploitation of CVE-2026-59293 in the wild and no public exploit code.

## Other vulnerabilities in Spring Integration

- [CVE-2026-59324](https://insights.sbomify.com/CVE-2026-59324/): fluxTransform shared RequestMessageHolder causes cross-message header leakage under async fluxFunction (high 8.2)
- [CVE-2026-59307](https://insights.sbomify.com/CVE-2026-59307/): Deserialization allow-list silently bypassed: setBeanClassLoader replaces deserializer but mapper keeps stale reference (high 8.0)
- [CVE-2026-40987](https://insights.sbomify.com/CVE-2026-40987/): Spring Integration File Support: FTP/SFTP/SMB server can write arbitrary files anywhere on the client filesystem (high 7.1)
- [CVE-2026-59311](https://insights.sbomify.com/CVE-2026-59311/): Fixed predictable /tmp/ziptransformer work directory enables symlink pre-creation (medium 6.8)
- [CVE-2026-59274](https://insights.sbomify.com/CVE-2026-59274/): Unbounded decompression in UnZipTransformer enables zip-bomb DoS (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59293 and fix it if it is affected.

What it is: CVE-2026-59293 is a medium-severity vulnerability in Spring Integration, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59293 in the wild and no public exploit code.

Affected product: Spring Integration. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59293/ (Markdown: https://insights.sbomify.com/CVE-2026-59293/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59293
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59293
- OSV: https://osv.dev/vulnerability/CVE-2026-59293

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59293/
Summaries are generated and may contain mistakes; the official description above is the record.