Description
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.
References7
- github.com/rabbitmq/rabbitmq-java-client/commit/1e7deb2e6020c97…
- github.com/rabbitmq/rabbitmq-java-client/commit/a4bf571dd368765…
- github.com/rabbitmq/rabbitmq-java-client/pull/1999
- github.com/rabbitmq/rabbitmq-java-client/pull/2001
- github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.33.0
- github.com/rabbitmq/rabbitmq-java-client/security/advisories/GH…
- github.com/rabbitmq/rabbitmq-java-client/security/advisories/GH…
Metrics
- CVSS 4.0
-
5.1
MEDIUM
Score source: CNA
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/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 - EPSS — exploit probability
- 0% percentile: 24 · as of 11 November 2026
- CWE
- CWE-295
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.