VMwareCVE-2026-59320
VMware Spring AMQP: resource leak
Medium6.5CVE-2026-59320 · Published Aug 27, 2026 · updated Aug 31, 2026
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 versions
| Package | Affected | Fixed in |
|---|---|---|
| Spring AMQP Product | <= 4.1.0 | No fix yet |
Details and references
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Severity from
- the vendor (its own CVE record or advisory)
- Weakness
- CWE-772
More VMware advisories
All VMware| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Aug 27 | VMware Spring Integration: race condition | Medium4.2 | No fix yet |
| Aug 27 | VMware Spring Integration: improper input validation | Medium6.3 | No fix yet |
| Aug 27 | VMware Spring Integration: race condition | High8.2 | No fix yet |
| Aug 27 | VMware Spring Integration: unsafe deserialization | High8.0 | No fix yet |
| Aug 27 | VMware Spring Integration: link following | Medium6.8 | No fix yet |
| Aug 27 | Spring MVC applications using the functional web framework are vulnerable to... | Critical9.8 | No fix yet |