Read the docs
TI-2026-52879 Aliases CVE-2026-75516GHSA-jh4v-gfqj-7rhx

RabbitMQ Java client: Frame-level OOM: Math.min(maxInboundMessageBodySize, 0) defeats frame size enforcement

Priority MEDIUM 44CWE-770Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
Denial of service
Confidentiality · integrity · availability
None · None · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-770.

Summary

The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.34.0, AMQConnection.start() applies Math.min(maxInboundMessageBodySize, frameMax) after Connection.Tune negotiation even though AMQP defines frameMax value zero as unlimited and ConnectionFactory.DEFAULT_FRAME_MAX is zero. When the client default and server-negotiated value are both zero, the result is passed to Utils.framePayloadLimit(int), which interprets zero as Integer.MAX_VALUE and disables the configured maxInboundMessageBodySize cap. A malicious AMQP server, or a man-in-the-middle attacker able to modify Connection.Tune and inject frames into the connection, can then send an oversized frame of any frame type, causing Frame.readFrom() to allocate a large byte array before content-level validation and potentially terminate the client process through memory exhaustion. This issue is fixed in version 5.34.0.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00552 46th percentileScored 2026-11-07
Fix Fixed rabbitmq-java-client (rabbitmq): 5.34.0com.rabbitmq:amqp-client (Maven): 5.34.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
rabbitmqrabbitmq-java-clientbefore 5.34.05.34.0Patch availableCNA
—com.rabbitmq:amqp-client (Maven)before 5.34.05.34.0Patch availableGHSA-jh4v-gfqj-7rhx
  • rabbitmq-java-client Vendorrabbitmq Affected before 5.34.0 Fixed in 5.34.0 Patch available CNA
  • com.rabbitmq:amqp-client (Maven) Vendor— Affected before 5.34.0 Fixed in 5.34.0 Patch available GHSA-jh4v-gfqj-7rhx

Remediation

  • Fix · CNA rabbitmq-java-client (rabbitmq) Fixed in 5.34.0
  • Fix · GHSA-jh4v-gfqj-7rhx com.rabbitmq:amqp-client (Maven) Fixed in 5.34.0 Advisory →

Vendor assessments

Red Hat

Red Hat rating: Important. Red Hat's page for this CVE →

Not affected: 2 products
  • Red Hat Fuse 7
  • Red Hat build of Apache Camel 4 for Quarkus 3

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-75516
  2. 2026-10-03 Alias added: GHSA-jh4v-gfqj-7rhx

References

Advisory 1

Other 7

  • TI-2026-41154 Improper authentication in rabbitmq-server CVSS 3.1CRITICAL 10.0
  • TI-2026-41149 RabbitMQ: UNC SSRF affecting the management UI on Windows CVSS 3.1CRITICAL 10.0
  • TI-2026-41158 Resource allocation without limits in rabbitmq-server CVSS 3.1HIGH 7.5
  • TI-2026-47695 RabbitMQ: OAuth2 Client Secret Exposed via Unauthenticated JavaScript Endpoint CVSS 4.0HIGH 8.2
  • TI-2026-47694 RabbitMQ: JWKS Fetch Ignores HTTP Response Status Code - Signing Key Destruction Causes Authentication DoS CVSS 4.0HIGH 8.2
  • TI-2026-45167 RabbitMQ Java client: Unvalidated Class.forName in JSON-RPC ProcedureDescription enables arbitrary class loading CVSS 4.0HIGH 7.5
See all 100 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences