CVE-2026-59320 In Spring AMQP the link credit never replenished on listener exception path
Attackers can cause permanent message delivery stalls in Spring AMQP by triggering listener exceptions, requiring a non-default error handler configuration.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-59320?
CVE-2026-59320 is a medium-severity denial of service vulnerability in Spring AMQP, published on 27 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
When a container-level ErrorHandler is configured (the mitigation for finding 221000), each delivery whose processing throws still permanently consumes one link credit. After initialCredits (default 100) failing messages the receiver's credit reaches zero and the broker stops delivering, leaving the listener silently stalled while isRunning() remains true. Spring AMQP 4.1.0
Weakness: CWE-772
Which versions are affected by CVE-2026-59320?
It affects 1 product.
Products include Vmware Spring Advanced Message Queuing Protocol.
How do I fix CVE-2026-59320?
No fix has been published for CVE-2026-59320 yet. Limit exposure of the affected software until one is available.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2026-59320 being exploited?
There is no known exploitation of CVE-2026-59320 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-59275 Deserialization in Spring AMQP
- 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-c8qp-wm54-v9v5.