CVE-2026-75516: CWE-770: Allocation of Resources Without Limits or Throttling in rabbitmq rabbitmq-java-client
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.
AI Analysis
Technical Summary
The RabbitMQ Java client library versions before 5.34.0 incorrectly handle the frame size limit during AMQP Connection.Tune negotiation. When both client default and server-negotiated frameMax values are zero (indicating unlimited), the client disables the maxInboundMessageBodySize cap by interpreting zero as Integer.MAX_VALUE. This allows a malicious AMQP server or a man-in-the-middle attacker to send an oversized frame, causing Frame.readFrom() to allocate a large byte array before validating content size. This can exhaust memory and terminate the client process. The vulnerability is addressed in version 5.34.0.
Potential Impact
An attacker controlling the AMQP server or able to modify Connection.Tune messages can exploit this flaw to send oversized frames that cause the client to allocate excessive memory. This can lead to denial of service by crashing the client application due to memory exhaustion. There is no indication of privilege escalation or data compromise from the provided data.
Mitigation Recommendations
Upgrade the rabbitmq-java-client library to version 5.34.0 or later, where this issue is fixed. No other mitigations are specified or required according to the available information.
CVE-2026-75516: CWE-770: Allocation of Resources Without Limits or Throttling in rabbitmq rabbitmq-java-client
Description
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.
CVSS v4.0
Score 8.7high
Affected software
rabbitmq
rabbitmq-java-client
pkg:maven/com.rabbitmq/rabbitmq-java-clientRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The RabbitMQ Java client library versions before 5.34.0 incorrectly handle the frame size limit during AMQP Connection.Tune negotiation. When both client default and server-negotiated frameMax values are zero (indicating unlimited), the client disables the maxInboundMessageBodySize cap by interpreting zero as Integer.MAX_VALUE. This allows a malicious AMQP server or a man-in-the-middle attacker to send an oversized frame, causing Frame.readFrom() to allocate a large byte array before validating content size. This can exhaust memory and terminate the client process. The vulnerability is addressed in version 5.34.0.
Potential Impact
An attacker controlling the AMQP server or able to modify Connection.Tune messages can exploit this flaw to send oversized frames that cause the client to allocate excessive memory. This can lead to denial of service by crashing the client application due to memory exhaustion. There is no indication of privilege escalation or data compromise from the provided data.
Mitigation Recommendations
Upgrade the rabbitmq-java-client library to version 5.34.0 or later, where this issue is fixed. No other mitigations are specified or required according to the available information.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-17T20:49:21.599Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6aaae43755bf5e2cf50475e8
Added to database: 09/16/2026, 18:47:19 UTC
Last enriched: 09/16/2026, 19:01:27 UTC
Last updated: 09/17/2026, 02:33:00 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.