RabbitMQ Java client accepts broker frames larger than the negotiated AMQP frame_max
GHSA-5xwg-cfvj-gff5 · CVE-2026-61634
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
Summary
The max body size was enforced to patch CVE-2023-46120, but even though that limit still works, the frame size itself still exceeds the given max size.
Root cause
The Java client records the AMQP 0-9-1 frame_max negotiated during connection tuning, but the socket inbound frame reader continues to validate broker-controlled payload lengths against the much larger maxInboundMessageBodySize limit. A broker peer can therefore send a method frame whose payload is larger than the negotiated frame_max, have it allocated and decoded, and complete the connection handshake instead of being rejected as a protocol violation.
Reported by Team Atlanta.
References
- WEB https://github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-5xwg-cfvj-gff5
- WEB https://github.com/rabbitmq/rabbitmq-java-client/pull/1994
- WEB https://github.com/rabbitmq/rabbitmq-java-client/pull/1995
- WEB https://github.com/rabbitmq/rabbitmq-java-client/commit/08790f09686173eb17b48d08a25edcb32e71a591
- WEB https://github.com/rabbitmq/rabbitmq-java-client/commit/b491075f42e89967610c40beded68d3680cfd472
- PACKAGE https://github.com/rabbitmq/rabbitmq-java-client
- WEB https://github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.33.0
Ready to move
Start Securing
Free, no credit card | First findings in minutes