6.5
Medium
CVE-2026-59320 When a container-level ErrorHandler is configured (the mitigation for finding 221000), each delivery whose processing…
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
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Spring AMQP | 4.1.0 | No fix stated |
References
- spring.io spring.io
Timeline
- Published
- Last modified
Other CVEs of Spring AMQP
The 8 CVEs of Spring AMQP →
CVE-2026-59272
Any application shipping logs to RabbitMQ over TLS via the Log4j2 appender, relying on the documented default, is…
6.8
Medium
CVE-2026-59275
A single hostile AMQP message can terminate the entire consumer JVM (System.exit(99)), not just the listener thread —…
6.6
Medium
CVE-2026-59271
When the RabbitMQ management aliveness check fails, the configured admin password is embedded in cleartext in the thrown…
5.3
Medium
CVE-2026-47860
An attacker who can publish to a queue consumed by an application that has enabled message decompression can crash the…
6.5
Medium