Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/rabbitmq/rabbitmq-java-client/commit/1e7deb2e6020c9793a81385a
- https://github.com/rabbitmq/rabbitmq-java-client/commit/a4bf571dd368765baaa9cecf
- https://github.com/rabbitmq/rabbitmq-java-client/pull/1999
- https://github.com/rabbitmq/rabbitmq-java-client/pull/2001
- https://github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.33.0
- https://github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-5m9f-r
- https://github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-5m9f-r
FAQ
What is CVE-2026-63336?
CVE-2026-63336 is a documented vulnerability. 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 Conn...
How severe is CVE-2026-63336?
CVSS scoring is not yet available for CVE-2026-63336. Check NVD for updates.
Is there a patch for CVE-2026-63336?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.