Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-5m9f-rphj-c435 | RabbitMQ Java client: TrustEverythingTrustManager used by default in useSslProtocol() enables MITM |
Tue, 18 Aug 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 18 Aug 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | RabbitMQ Java client: TrustEverythingTrustManager used by default in useSslProtocol() enables MITM | |
| Weaknesses | CWE-295 | |
| References |
|
|
| Metrics |
cvssV4_0
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-08-18T17:34:30.102Z
Reserved: 2026-07-16T14:14:24.385Z
Link: CVE-2026-63336
Updated: 2026-08-18T17:31:20.443Z
Status : Received
Published: 2026-08-18T17:17:00.280
Modified: 2026-08-18T18:19:10.150
Link: CVE-2026-63336
No data.
OpenCVE Enrichment
Updated: 2026-08-18T17:30:15Z
Github GHSA