Allocation of Resources Without Limits or Throttling Affecting com.rabbitmq:amqp-client package, versions [,5.34.0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Allocation of Resources Without Limits or Throttling vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-JAVA-COMRABBITMQ-19963954
- published20 Sept 2026
- disclosed17 Sept 2026
- creditlucianjohnhouse
Introduced: 17 Sep 2026
NewCVE-2026-75516 (opens in a new tab)How to fix?
Upgrade com.rabbitmq:amqp-client to version 5.34.0 or higher.
Overview
Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to the inbound frame size handling in AMQConnection.java. An attacker can trigger excessive frame allocation and crash the client by negotiating frame_max=0 and then sending an oversized AMQP frame. The vulnerable code derives the inbound frame payload limit with Math.min(this.maxInboundMessageBodySize, frameMax), so a negotiated zero-valued frameMax is treated as a literal limit of 0 and defeats the configured inbound cap. Because frame.readFrom() allocates based on that effective limit, a malicious broker or MITM can force the client to accept a huge frame and exhaust memory during connection processing.