CVE-2026-59320

In Spring AMQP the link credit never replenished on listener exception path

Published Aug 27, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
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

Analysis

AI-generated

Technical impact

When a container-level ErrorHandler is enabled in Spring AMQP, each message that throws an exception consumes one broker link credit that is never replenished. After the configured initialCredits (default 100) have been exhausted, the receiver’s credit reaches zero and the broker stops delivering new messages. The listener thread continues to report that it is running, causing a silent stall of the consumer. Based on the description, this flaw leads to a denial of service that stalls the consumer thread. The improper resource handling aligns with the CWE-772 classification.

Affected Systems

The issue impacts any deployment of the Spring AMQP library that uses a container-level ErrorHandler. Based on the description, the flaw is known in Spring AMQP 4.1.0 and thus applies to that version and earlier releases that rely on the default initialCredits setting of 100. The vulnerability affects application code that integrates Spring AMQP and does not alter broker behaviour; the broker itself remains functional until credit exhaustion occurs.

Risk and Exploitability

The CVSS score of 6.5 indicates moderate severity. The EPSS score is 0.00289 (<1%), indicating a very low probability of exploitation, and the vulnerability is not listed in the CISA KEV catalog, implying limited evidence of active exploitation. Exploitation requires misbehavior within the application: a configured ErrorHandler and repeated message processing failures. An attacker who can influence the application to generate such failures could precipitate the DoS. Because exploitation does not rely on special network traffic, the risk is primarily operational rather than remote, though any environment that accepts untrusted input could be targeted by an attacker who can exacerbate failures.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Spring AMQP to the newest release that contains a fix for the credit replenishment logic.
  • If an upgrade is not possible immediately, reconfigure the container-level ErrorHandler so it does not consume link credit when a message fails, or temporarily disable the ErrorHandler.
  • Adjust the initialCredits setting to a lower value or monitor credit usage; consider reducing to a value that mitigates exhaustion during periods of failure.
  • Restart the listener containers after configuration changes to restore normal credit flow.

Generated by OpenCVE AI on August 29, 2026 at 02:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
References
History
Type Values Removed Values Added
First Time appeared Vmware
Vmware spring Advanced Message Queuing Protocol
CPEs cpe:2.3:a:vmware:spring_advanced_message_queuing_protocol:*:*:*:*:*:*:*:*
Vendors & Products Vmware
Vmware spring Advanced Message Queuing Protocol
Type Values Removed Values Added
Weaknesses CWE-400
Type Values Removed Values Added
Weaknesses CWE-772
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-400
Type Values Removed Values Added
First Time appeared Spring
Spring spring Amqp
Vendors & Products Spring
Spring spring Amqp
Type Values Removed Values Added
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
Title In Spring AMQP the link credit never replenished on listener exception path
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-772

    Missing Release of Resource after Effective Lifetime

Sources

Status
PUBLISHED
Assigner
vmware
Published
Updated
Aug 28, 2026, 10:46 PM
Reserved
Jul 4, 2026, 6:14 PM
Status
Analyzed
Published
Aug 27, 2026, 8:17 PM
Modified
Aug 31, 2026, 5:19 PM