Quick answers
- Is CVE-2026-59293 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59293 being exploited in the wild.
- How severe is CVE-2026-59293?
- Medium severity, with a CVSS score of 6.6, published 27 August 2026.
- Which products and versions are affected?
- Pivotal Spring Integration 6.4.0–6.4.12, 6.5.0–6.5.10, 7.0.0–7.0.5.
- Is there a fix for CVE-2026-59293?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-59293 attacked?
- It is attacked over the network or from the adjacent network, in a software library.
- Am I affected by CVE-2026-59293?
- Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a protocol downgrade issue in the jCIFS CIFS client library bundled with Spring Integration. Unless the application explicitly sets smbMinVersion, the client will negotiate down to SMB1/CIFS, which lacks mandatory message signing and encryption. This allows an attacker on the network (adjacent network access) to perform NTLM relay attacks and man-in-the-middle content tampering. The vulnerability affects Spring Integration versions 6.4.0–6.4.12, 6.5.0–6.5.10, and 7.0.0–7.0.5; version 7.1.0 and later default to a higher minimum SMB version. Mitigation requires upgrading to a patched version or explicitly configuring smbMinVersion in the application.
Affected products
- Pivotal Spring Integration 6.4.0–6.4.12, 6.5.0–6.5.10, 7.0.0–7.0.5
Timeline
- 2026-08-27: disclosed