The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.33.0, com.rabbitmq.client.ConnectionFactory.useSslProtocol() and ConnectionFactory.useSslProtocol(String) configure com.rabbitmq.client.TrustEverythingTrustManager and leave hostname verification disabled, causing arbitrary server certificates, including self-signed certificates, to be accepted. A network attacker able to intercept a TLS connection can impersonate the RabbitMQ broker, read protected AMQP traffic, and modify traffic without certificate or hostname validation. The fix changes the production TLS helpers to use the JVM default trust store and enables hostname verification, while retaining an explicitly named development-only no-verification helper. 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, com.rabbitmq.client.ConnectionFactory.useSslProtocol() and
    ConnectionFactory.useSslProtocol(String) configure com.rabbitmq.client.TrustEverythingTrustManager and
    leave hostname verification disabled, causing arbitrary server certificates, including self-signed
    certificates, to be accepted. A network attacker able to intercept a TLS connection can impersonate the
    RabbitMQ broker, read protected AMQP traffic, and modify traffic without certificate or hostname
    validation. The fix changes the production TLS helpers to use the JVM default trust store and enables
    hostname verification, while retaining an explicitly named development-only no-verification helper. This
    issue is fixed in version 5.33.0. (CVE-2026-63336)

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, com.rabbitmq.client.ConnectionFactory.useSslProtocol() and     ConnectionFactory.useSslProtocol(String) configure com.rabbitmq.client.TrustEverythingTrustManager and     leave hostname verification disabled, causing arbitrary server certificates, including self-signed     certificates, to be accepted. A network attacker able to intercept a TLS connection can impersonate the     RabbitMQ broker, read protected AMQP traffic, and modify traffic without certificate or hostname     validation. The fix changes the production TLS helpers to use the JVM default trust store and enables     hostname verification, while retaining an explicitly named development-only no-verification helper. This     issue is fixed in version 5.33.0. (CVE-2026-63336)

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

ID	Name	Product	Family	Type	Severity
465078	Echo: com.rabbitmq:amqp-client: security update to 5.33.0	Tenable Cloud Security	Echo Local Security Checks	Local	medium
465078	Echo: com.rabbitmq:amqp-client: security update to 5.33.0	Tenable Self-Hosted Container Security	Echo Local Security Checks	Local	medium
338046	Linux Distros Unpatched Vulnerability : CVE-2026-63336	Nessus	Misc.	Local	medium
446066	SCA: security update for com.rabbitmq:amqp-client (GHSA-5m9f-rphj-c435)	Tenable Cloud Security	SCA Checks	Local	medium
446066	SCA: security update for com.rabbitmq:amqp-client (GHSA-5m9f-rphj-c435)	Tenable Self-Hosted Container Security	SCA Checks	Local	medium

Detections

Analytics

CVE-2026-63336

medium

Tenable Plugins

medium

medium

medium

medium

medium