CVE-2026-69219: RabbitMQ Java client memory allocation DoS in ValueReader

CVE-2026-69219 · Severity: high · CVSS 4 · Published 2026-08-18

RabbitMQ's Java AMQP client library contains a vulnerability in its message parsing code that can be exploited by a malicious server to crash the entire JVM. When processing string or binary data fields from AMQP protocol messages, the library allocates memory based on a size value sent by the server without validating whether that size is reasonable. An attacker can declare a ~2 GB string field, forcing the JVM to attempt a massive memory allocation that exceeds available resources, resulting in an out-of-memory crash that brings down any application using this library.

Technologies: com.rabbitmq:amqp-client (Maven), RabbitMQ Amqp-Client. Vendors: Maven, RabbitMQ.

Quick answers

Is CVE-2026-69219 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-69219 being exploited in the wild.
How severe is CVE-2026-69219?
High severity, with a CVSS score of 4, published 18 August 2026.
Which products and versions are affected?
com.rabbitmq:amqp-client (Maven) <= 5.33.0, ECOSYSTEM:introduced=0,fixed=5.33.1.
Is there a fix for CVE-2026-69219?
Yes. com.rabbitmq:amqp-client (Maven): upgrade to 5.33.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-69219 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-69219?
Check whether you run com.rabbitmq:amqp-client (Maven) or RabbitMQ Amqp-Client at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • com.rabbitmq:amqp-client (Maven): upgrade to 5.33.1 or later
    # set com.rabbitmq:amqp-client to 5.33.1 in your pom.xml or build.gradle

Technical details

The vulnerability exists in the `ValueReader.readBytes()` method in `src/main/java/com/rabbitmq/client/impl/ValueReader.java`. The method reads a 32-bit integer from the wire to determine the size of a byte array, then immediately allocates that array without validating the size against frame boundaries or the negotiated maximum frame size (default 131,072 bytes). A malicious AMQP server sends a LongString field (AMQP type tag 'S') with declared length 0x7FFFFFFE (2,147,483,646 bytes), which passes the check `contentLength < Integer.MAX_VALUE` and triggers `new byte[2147483646]`, causing an OutOfMemoryError before the `readFully()` call ever attempts to read data. This vulnerability is exploitable pre-authentication via the `connection.start` server-properties table, requiring only network access to an AMQP broker. The fix validates the declared content length against the frame's remaining bytes or maximum frame size before allocating memory. Patched in version 5.33.1.

Affected products

  • RabbitMQ amqp-client <= 5.33.0

Identifiers

  • CVE-2026-69219
  • GHSA-68mj-5wr7-6fgg

Timeline

  • 2026-07-09: disclosed: GitHub Security Advisory published
  • 2026-08-18: advisory: Updated in GitHub Advisory Database
  • 2026-08-18: patched: Version 5.33.1 released with fix

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.