CVE-2026-63336

Published: Ago 18, 2026 Last Modified: Ago 18, 2026
ExploitDB:
Other exploit source:
Google Dorks:
MEDIUM 5,1
Attack Vector: network
Attack Complexity: low
Privileges Required: low
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A

Description

AI Translation 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.

295

Improper Certificate Validation

Draft
Common Consequences
Security Scopes Affected:
Integrity Authentication
Potential Impacts:
Bypass Protection Mechanism Gain Privileges Or Assume Identity
Applicable Platforms
Technologies: Not Technology-Specific, Web Based, Mobile
View CWE Details
https://github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-5m9f-…
https://github.com/rabbitmq/rabbitmq-java-client/commit/1e7deb2e6020c9793a81385…
https://github.com/rabbitmq/rabbitmq-java-client/commit/a4bf571dd368765baaa9cec…
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-…