CVE-2026-61634: CWE-20: Improper Input Validation 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.33.0, the AMQP connection tuning path records the negotiated AMQP frame_max value, but src/main/java/com/rabbitmq/client/impl/SocketFrameHandler.java and NettyFrameHandlerFactory continue to validate broker-controlled frame payload lengths against maxInboundMessageBodySize because the negotiated limit is not applied consistently through setMaxInboundFramePayloadSize. A malicious or compromised broker can send a method frame larger than the negotiated frame_max during or after connection establishment, causing the client to allocate and decode a protocol-invalid frame instead of rejecting it with MalformedFrameException. The protocol violation can disrupt the affected connection and cause client-side denial of service. This issue is fixed in version 5.33.0.
AI Analysis
Technical Summary
The RabbitMQ Java client library before version 5.33.0 does not consistently enforce the negotiated AMQP frame_max size during connection tuning. Specifically, the SocketFrameHandler and NettyFrameHandlerFactory validate frame payload lengths against maxInboundMessageBodySize rather than the negotiated frame_max, allowing a broker to send method frames larger than the agreed limit. This improper input validation (CWE-20) can cause the client to process protocol-invalid frames instead of rejecting them, resulting in connection disruption and denial of service on the client side. The vulnerability is addressed in version 5.33.0.
Potential Impact
A malicious or compromised RabbitMQ broker can send oversized AMQP frames that violate the protocol, causing the client to allocate excessive memory and decode invalid frames. This leads to disruption of the affected connection and denial of service on the client side. There is no indication of privilege escalation or remote code execution.
Mitigation Recommendations
Upgrade the rabbitmq-java-client library to version 5.33.0 or later, where this issue is fixed. No other mitigation or workaround is documented. Patch status is not explicitly stated but the fix is confirmed in version 5.33.0.
CVE-2026-61634: CWE-20: Improper Input Validation 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.33.0, the AMQP connection tuning path records the negotiated AMQP frame_max value, but src/main/java/com/rabbitmq/client/impl/SocketFrameHandler.java and NettyFrameHandlerFactory continue to validate broker-controlled frame payload lengths against maxInboundMessageBodySize because the negotiated limit is not applied consistently through setMaxInboundFramePayloadSize. A malicious or compromised broker can send a method frame larger than the negotiated frame_max during or after connection establishment, causing the client to allocate and decode a protocol-invalid frame instead of rejecting it with MalformedFrameException. The protocol violation can disrupt the affected connection and cause client-side denial of service. This issue is fixed in version 5.33.0.
CVSS v4.0
Score 0.0none
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 before version 5.33.0 does not consistently enforce the negotiated AMQP frame_max size during connection tuning. Specifically, the SocketFrameHandler and NettyFrameHandlerFactory validate frame payload lengths against maxInboundMessageBodySize rather than the negotiated frame_max, allowing a broker to send method frames larger than the agreed limit. This improper input validation (CWE-20) can cause the client to process protocol-invalid frames instead of rejecting them, resulting in connection disruption and denial of service on the client side. The vulnerability is addressed in version 5.33.0.
Potential Impact
A malicious or compromised RabbitMQ broker can send oversized AMQP frames that violate the protocol, causing the client to allocate excessive memory and decode invalid frames. This leads to disruption of the affected connection and denial of service on the client side. There is no indication of privilege escalation or remote code execution.
Mitigation Recommendations
Upgrade the rabbitmq-java-client library to version 5.33.0 or later, where this issue is fixed. No other mitigation or workaround is documented. Patch status is not explicitly stated but the fix is confirmed in version 5.33.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-10T17:38:57.111Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a848e59c6e8be03327e6ad1
Added to database: 08/18/2026, 16:54:49 UTC
Last enriched: 08/18/2026, 17:08:29 UTC
Last updated: 10/02/2026, 02:46:05 UTC
Views: 56
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.