lowVulnerability
CVE-2026-61634
## 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.*
Properties
- ghsa_id
- GHSA-5xwg-cfvj-gff5
- severity
- low
- summary
- RabbitMQ Java client accepts broker frames larger than the negotiated AMQP frame_max
- cve_id
- CVE-2026-61634
- is_ghsa_only
- false
- ghsa_published
- 2026-08-18T16:36:29Z
- source_url
- https://github.com/advisories/GHSA-5xwg-cfvj-gff5
- ghsa_updated
- 2026-08-18T16:36:30Z
Related Entities (4)
VULNERABLE_TO (1)
←[Software]maven/com.rabbitmq:amqp-client
AFFECTS (1)
→[Software]maven/com.rabbitmq:amqp-client
HAS_WEAKNESS (1)
→[Weakness]Improper Input Validation
REPORTED_BY (1)
→[Source]GitHub Advisory Database
Explore deeper with Ninja Signal's threat intelligence graph