Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The RabbitMQ Java client (com.rabbitmq:amqp-client, Maven) versions before 5.34.0 are affected. When the negotiated frame-max is 0, the client's frame size limit is disabled, so a malicious AMQP server or man-in-the-middle can send a single oversized frame that causes the client to allocate up to about 2 GB and crash with an out-of-memory error. Upgrade to version 5.34.0 or later.
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 |
|---|---|---|---|---|
| 8.7 | High | 4.0 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0055, the 46th percentile, on 7 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-jh4v-gfqj-7rhx
- OSV: GHSA-jh4v-gfqj-7rhx
- github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-jh4v-gfqj-7rhx
- nvd.nist.gov/vuln/detail/CVE-2026-75516
- github.com/rabbitmq/rabbitmq-java-client/pull/2015
- github.com/rabbitmq/rabbitmq-java-client/pull/2016
- github.com/rabbitmq/rabbitmq-java-client/commit/6d7c2bfe89796ca34d3531098fb59dd657fea39e
- github.com/rabbitmq/rabbitmq-java-client/commit/e7f10bf99aee103dd9f64b3e52a725fc9f9d3763
- github.com/rabbitmq/rabbitmq-java-client
- github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.34.0