CVE-2026-61634

Published: Ago 18, 2026 Last Modified: Ago 18, 2026
ExploitDB:
Other exploit source:
Google Dorks:

Description

AI Translation Available

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.

20

Improper Input Validation

Stable
Common Consequences
Security Scopes Affected:
Availability Confidentiality Integrity
Potential Impacts:
Dos: Crash, Exit, Or Restart Dos: Resource Consumption (Cpu) Dos: Resource Consumption (Memory) Read Memory Read Files Or Directories Modify Memory Execute Unauthorized Code Or Commands
Applicable Platforms
Technologies: AI/ML
View CWE Details
https://github.com/rabbitmq/rabbitmq-java-client/commit/08790f09686173eb17b48d0…
https://github.com/rabbitmq/rabbitmq-java-client/commit/b491075f42e89967610c40b…
https://github.com/rabbitmq/rabbitmq-java-client/pull/1994
https://github.com/rabbitmq/rabbitmq-java-client/pull/1995
https://github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.33.0
https://github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-5xwg-…