DEBIAN-CVE-2026-61634
- Source
- https://security-tracker.debian.org/tracker/CVE-2026-61634
- Import Source
- https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-61634.json
- JSON Data
- https://api.osv.dev/v1/vulns/DEBIAN-CVE-2026-61634
- Upstream
- Published
- 2026-08-18T17:16:59Z
- Modified
- 2026-09-19T16:00:08Z
- Severity
-
- 0.0 (None) CVSS_V4 - CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X CVSS Calculator
- Summary
- [none]
- Details
-
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.
- References
Affected packages
Debian:12 / rabbitmq-java-client
Package
- Name
- rabbitmq-java-client
- Purl
- pkg:deb/debian/rabbitmq-java-client?arch=source&distro=bookworm
Debian:13 / rabbitmq-java-client
Package
- Name
- rabbitmq-java-client
- Purl
- pkg:deb/debian/rabbitmq-java-client?arch=source&distro=trixie