{"id":"CVE-2026-61634","title":"The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes","summary":"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/r…","severity":"low","cwe":["CWE-20"],"vendor":"rabbitmq","product":"com.rabbitmq:amqp-client","affected":["com.rabbitmq:amqp-client < 5.33.0"],"patched":["com.rabbitmq:amqp-client 5.33.0"],"published":"2026-08-18","updated":"2026-09-10","sourceUpdated":"2026-09-10T20:30:11.423","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-61634","references":[{"url":"https://github.com/rabbitmq/rabbitmq-java-client/commit/08790f09686173eb17b48d08a25edcb32e71a591","label":"security-advisories@github.com"},{"url":"https://github.com/rabbitmq/rabbitmq-java-client/commit/b491075f42e89967610c40beded68d3680cfd472","label":"security-advisories@github.com"},{"url":"https://github.com/rabbitmq/rabbitmq-java-client/pull/1994","label":"security-advisories@github.com"},{"url":"https://github.com/rabbitmq/rabbitmq-java-client/pull/1995","label":"security-advisories@github.com"},{"url":"https://github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.33.0","label":"security-advisories@github.com"},{"url":"https://github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-5xwg-cfvj-gff5","label":"security-advisories@github.com"},{"url":"https://github.com/advisories/GHSA-5xwg-cfvj-gff5"}],"tags":["nvd","ghsa","maven"],"epss":0.00299,"epssPercentile":0.22827,"aliases":["GHSA-5xwg-cfvj-gff5"],"ecosystem":"maven","ingestedAt":"2026-08-18T17:20:36.448Z","slug":"CVE-2026-61634","body":"## Overview\n\nThe 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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.\n\n## Package advisory (CVE-2026-61634)\n\nAffected packages:\n\n- `com.rabbitmq:amqp-client < 5.33.0`\n\nPatched in:\n\n- `com.rabbitmq:amqp-client 5.33.0`\n\nSource: https://github.com/advisories/GHSA-5xwg-cfvj-gff5","depth":"sunlit","depthScore":14,"depthScoreParts":{"impact":13.8,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}