Listener denial of service via exhausted link credit
Published Aug 27, 2026 · Updated Aug 27, 2026
Denial of service in Spring AMQP 4.1.0 allows remote authenticated users to stall AMQP 1.0 listeners with failing deliveries. On the listener-exception path, a configured container ErrorHandler fails to replenish the receiver credit consumed by each delivery whose processing throws. An affected application must use the container-level ErrorHandler; after the initial credits are consumed, the broker stops delivery while isRunning() remains true.
Summary
What happened
Denial of service in Spring AMQP 4.1.0 allows remote authenticated users to stall AMQP 1.0 listeners with failing deliveries. On the listener-exception path, a configured container ErrorHandler fails to replenish the receiver credit consumed by each delivery whose processing throws. An affected application must use the container-level ErrorHandler; after the initial credits are consumed, the broker stops delivery while isRunning() remains true.
The record
- CVE
- CVE-2026-59320
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- Spring
- Product
- Spring AMQP
- Classifications
- CWE-772, T1499.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo