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.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - 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. (CVE-2026-61634)

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch 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. (CVE-2026-61634)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Type	Severity
458997	Echo: com.rabbitmq:amqp-client: security update to 5.33.0	Tenable Cloud Security	Echo Local Security Checks	Local	high
458997	Echo: com.rabbitmq:amqp-client: security update to 5.33.0	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	high
338047	Linux Distros Unpatched Vulnerability : CVE-2026-61634	Nessus	Misc.	Local	high
446063	SCA: security update for com.rabbitmq:amqp-client (GHSA-5xwg-cfvj-gff5)	Tenable Cloud Security	SCA Checks	Local	info
446063	SCA: security update for com.rabbitmq:amqp-client (GHSA-5xwg-cfvj-gff5)	Tenable Self-Hosted Container Security	SCA Checks	Local	info

Detections

Analytics

CVE-2026-61634

info

Tenable Plugins

high

high

high

info

info