Quick answers
- Is CVE-2026-59274 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59274 being exploited in the wild.
- How severe is CVE-2026-59274?
- Medium severity, with a CVSS score of 6.5, published 27 August 2026.
- Which products and versions are affected?
- VMware Spring Integration 6.4.0–6.4.12, 6.5.0–6.5.10, 7.0.0–7.0.5, 7.1.0.
- Is there a fix for CVE-2026-59274?
- 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-59274 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-59274?
- Check whether you run VMware Spring Integration at an affected version. 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 UnZipTransformer in Spring Integration lacks input validation on decompressed entry size and total entry count when extracting ZIP archives. This is a classic zip bomb or decompression bomb vulnerability (CWE-409). An attacker with network access can craft a compressed archive containing highly compressed data that expands to gigabytes or terabytes when decompressed, exhausting JVM heap memory and triggering an OutOfMemoryError. The vulnerability requires the application to be configured to use UnZipTransformer and process untrusted ZIP input, but no authentication or user interaction is needed once such a flow is active. The fix involves adding resource limits (maximum decompressed size per entry and total entry count) before decompression.
Affected products
- VMware Spring Integration 6.4.0–6.4.12, 6.5.0–6.5.10, 7.0.0–7.0.5, 7.1.0
Timeline
- 2026-08-27: disclosed