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) versions before 5.18.0 do not apply the configured maximum body length when receiving messages. An attacker who can send a very large message to a queue a consumer reads from can exhaust that consumer's memory and cause an OutOfMemoryError. Upgrade to amqp-client 5.18.0 or later. The source gives few details on other workarounds.
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 |
|---|---|---|---|---|
| 4.9 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.013, the 71st percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:18 UTC First seen by agentprime
- 31 Oct 2026, 14:18 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-mm8h-8587-p46h
- OSV: GHSA-mm8h-8587-p46h
- github.com/rabbitmq/rabbitmq-java-client/security/advisories/GHSA-mm8h-8587-p46h
- nvd.nist.gov/vuln/detail/CVE-2023-46120
- github.com/rabbitmq/rabbitmq-java-client/issues/1062
- github.com/rabbitmq/rabbitmq-java-client/commit/714aae602dcae6cb4b53cadf009323ebac313cc8
- github.com/rabbitmq/rabbitmq-java-client
- github.com/rabbitmq/rabbitmq-java-client/releases/tag/v5.18.0