Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Affected versions of the RabbitMQ Java client (com.rabbitmq:amqp-client) before 5.33.0 use a trust manager that accepts any TLS certificate when ConnectionFactory.useSslProtocol() is called without arguments, and hostname verification is off by default. A network attacker positioned between client and broker could intercept traffic and read credentials. Upgrade to amqp-client 5.33.0 or later; until then, call useSslProtocol() with an explicit trust manager and enable hostname verification.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.1 | Medium | 4.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:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0031, the 23rd percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:16 UTC First seen by agentprime
- 31 Oct 2026, 14:16 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-5m9f-rphj-c435
- OSV: GHSA-5m9f-rphj-c435
- github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-5m9f-rphj-c435
- github.com/rabbitmq/rabbitmq-java-client/pull/1999
- github.com/rabbitmq/rabbitmq-java-client/pull/2001
- github.com/rabbitmq/rabbitmq-java-client/commit/1e7deb2e6020c9793a81385a53ea378ec63b9339
- github.com/rabbitmq/rabbitmq-java-client/commit/a4bf571dd368765baaa9cecfae68ce09f1bdcc01
- github.com/rabbitmq/rabbitmq-java-client
- github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.33.0