CVE-2026-59275 Deserialization in Spring AMQP
A remote attacker can terminate the JVM via a malicious AMQP message exploiting a deserialization flaw in Spring AMQP, causing denial of service.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-59275?
CVE-2026-59275 is a medium-severity unsafe deserialization vulnerability in Spring AMQP, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
A single hostile AMQP message can terminate the entire consumer JVM (System.exit(99)), not just the listener thread — full availability loss for every workload co-located in that process. Spring AMQP 4.1.0 Spring AMQP 4.0.0 - 4.0.4 Spring AMQP 3.2.0 - 3.2.12 Spring AMQP 2.4.18 and earlier
Weakness: CWE-502
Which versions are affected by CVE-2026-59275?
It affects 1 product.
Products include Vmware Spring Advanced Message Queuing Protocol.
How do I fix CVE-2026-59275?
Upgrade to a fixed version.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2026-59275 being exploited?
There is no known exploitation of CVE-2026-59275 in the wild and no public exploit code.
Other vulnerabilities in Spring AMQP
- CVE-2026-59272 Log4j2 AmqpAppender disables TLS hostname verification by default
- CVE-2026-59320 In Spring AMQP the link credit never replenished on listener exception path
- CVE-2026-47860 Unbounded decompression of attacker-supplied compressed message bodies
- CVE-2021-22095 Deserialization of Untrusted Data in Spring AMQP
- CVE-2021-22097 Deserialization of Untrusted Data in Spring AMQP
Sources
Also known as GHSA-h7q9-2m8q-h4jr.