CVE-2026-63336: rabbitmq-java-client · Improper Certificate Validation
Affects rabbitmq-java-clientSource CVE Database V5
Not known to be exploited · CVSS 5.1 Medium : upgrade to 5.33.0 when convenient.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.33.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade rabbitmq-java-client and com.rabbitmq/rabbitmq-java-client to 5.33.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| rabbitmqrabbitmq-java-client | Affected
| Fixed in
|
Mavencom.rabbitmq/rabbitmq-java-clientpkg:maven/com.rabbitmq/rabbitmq-java-clientOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to rabbitmq-java-client version 5.33.0 or later, where the vulnerability is fixed by enabling proper certificate validation and hostname verification by default. Avoid using the development-only no-verification helper in production environments. Patch status is not explicitly stated but the fix is included in version 5.33.0, so upgrading to this version or later is the recommended remediation.
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.
References
- github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-5m9f-rphj-c435 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-java-client/pull/1999 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-java-client/pull/2001 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-java-client/commit/1e7deb2e6020c9793a81385a53ea378ec63b9339 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-java-client/commit/a4bf571dd368765baaa9cecfae68ce09f1bdcc01 (opens in a new tab)
- github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.33.0 (opens in a new tab)