Quick answers
- Is CVE-2026-59275 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59275 being exploited in the wild.
- How severe is CVE-2026-59275?
- Medium severity, with a CVSS score of 6.6, published 27 August 2026.
- Which products and versions are affected?
- VMware Spring AMQP 2.4.18 and earlier; 3.2.0 through 3.2.12; 4.0.0 through 4.0.4; 4.1.0.
- Is there a fix for CVE-2026-59275?
- 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-59275 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-59275?
- Check whether you run VMware Spring AMQP 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
Spring AMQP contains a flaw in message handling that allows a hostile AMQP message to trigger an uncaught exception leading to JVM termination (System.exit(99)). The vulnerability affects the message listener and consumer logic, which processes untrusted network messages without proper exception handling. An attacker with the ability to send messages to the AMQP broker can craft a specific message payload that exploits this condition. No authentication or special preconditions are required beyond network access to the AMQP broker. The result is a denial-of-service condition affecting all workloads running in the targeted process. Patches are available in Spring AMQP 2.4.19+, 3.2.13+, and 4.0.5+.
Affected products
- VMware Spring AMQP 2.4.18 and earlier; 3.2.0 through 3.2.12; 4.0.0 through 4.0.4; 4.1.0
Timeline
- 2026-08-27: disclosed