Description
The RabbitMQ Java client library allows Java and JVM-based applications to connect to and interact with RabbitMQ nodes. Prior to 5.35.0, ConnectionFactoryConfigurator.load() includes the raw uri value in wrapped exceptions when AMQP URI parsing fails. Because the URI may contain a plaintext username and password, startup logs, application performance monitoring systems, CI logs, and copied stack traces can disclose broker credentials to users who should not have access to them. This issue is fixed in version 5.35.0.
Affected products
vmware: rabbitmq java client
References4
- github.com/rabbitmq/rabbitmq-java-client/security/advisories/GH… ExploitVendor Advisory
- github.com/rabbitmq/rabbitmq-java-client/commit/daca1875cdb8b8c… Patch
- github.com/rabbitmq/rabbitmq-java-client/pull/2052 Issue TrackingPatch
- github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.35.0 Release Notes
Metrics
- CVSS 3.1
-
5.5
MEDIUM
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N - CVSS 4.0
-
5.7
MEDIUM
Score source: CNA
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/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: 15 · as of 10 November 2026
- CWE
- CWE-209
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.