Memory Allocation with Excessive Size Value Affecting com.rabbitmq:amqp-client package, versions [,5.33.1)
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 applications- Snyk IDSNYK-JAVA-COMRABBITMQ-18958660
- published19 Aug 2026
- disclosed18 Aug 2026
- creditlucianjohnhouse
Introduced: 18 Aug 2026
NewCVE-2026-69219 (opens in a new tab)How to fix?
Upgrade com.rabbitmq:amqp-client to version 5.33.1 or higher.
Overview
Affected versions of this package are vulnerable to Memory Allocation with Excessive Size Value via the readBytes() method in src/main/java/com/rabbitmq/client/impl/ValueReader.java. An attacker can trigger a JVM OutOfMemoryError by sending an AMQP field or long string with a declared length that causes the reader to allocate a byte array before verifying that the frame actually contains that many bytes.
The vulnerable code trusts the wire length prefix and creates new byte[(int)contentLength] for any value below Integer.MAX_VALUE. A malicious peer can supply a near-2GB length and crash the client process before readFully() can reject the frame.