Servers and applications
GHSA-pj8f-mw2q-3xjj
RabbitMQ consistent-hash exchange: empty array crashes DLX queue processes
- Severity
- Low 2.3
- Published
- 18 Aug 2026
- Last changed
- 18 Aug 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 3.13.20, 4.0.25, 4.1.16, 4.2.10, 4.3.5
- Attack
- Over the network · Only under certain conditions · Needs a user account · No user action needed
- Attacker can
- Slow it down
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N- Sources
- Project advisories (GitHub)
Description
An x-consistent-hash exchange configured with hash-header accepts an AMQP field-array as the selected hash value. RabbitMQ preserves an empty AMQP array as the Erlang empty list [].
When the exchange has at least two buckets, its routing function treats lists by hashing their first element and calls hd([]), raising badarg.
A direct publish closes the publisher's channel. More importantly, if a classic queue dead-letters an attacker-controlled message through the exchange, the routing exception occurs inside the victim queue process. A persistent poison message is retried when the queue restarts, repeatedly crashing the queue until its supervisor exhausts restart attempts. The attacker publication is confirmed and the attacker's channel survives because the exception occurs later in the victim's DLX path.
- rabbitmq_consistent_hash_exchange is enabled.
- An x-consistent-hash exchange uses hash-header = h.
- At least two queues or bucket weights are bound to that exchange.
Affected software
| Software | Affected versions |
|---|---|
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server |
|
About RabbitMQ
open source message broker, sometimes referred to as "Rabbit"
- Docker Hub pulls
- 3,918,841,187Docker Hub, 15 Nov 2026
- GitHub stars
- 13,973GitHub, 15 Nov 2026
- Forks
- 4,032GitHub, 15 Nov 2026
- Latest release
- v4.4.0GitHub, 15 Nov 2026
- Released
- 19 Oct 2026GitHub
- Developer
- Jean-Sébastien PédronWikidata
- License
- Mozilla Public License, version 2.0Wikidata
- Written in
- ErlangWikidata
- First published on GitHub
- 20 Sept 2010GitHub
Website Source code Docker image
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 4.4 | 4.4.0 | Until 31 Jul 2027 |
| 4.3 | 4.3.7 | Until 31 Jan 2027 |
| 4.2 | 4.2.9 | Ended 31 Jul 2026 |
| 4.1 | 4.1.8 | Ended 30 Jan 2026 |
| 4.0 | 4.0.9 | Ended 30 Apr 2025 |
| 3.13 | 3.13.7 | Ended 30 Sept 2024 |
From endoflife.date.
Vulnerabilities in RabbitMQ
- In our list
- 107
- Published in the last 12 months
- 89
- Critical, last 12 months
- 4
- High, last 12 months
- 22
- Known exploited
- 0
- GHSA-3wxh-g236-vm46LDAP authentication failures allow unauthenticated log amplificationHigh 8.2 25 Oct 2026
- GHSA-g73v-gcjq-2g4hAMQP message conversion can repeatedly disconnect AMQP 0-9-1 consumersMedium 6.3 25 Oct 2026
- GHSA-6wvj-vwrc-wcrmHTML injection in management UI OAuth login warningMedium 5.7 25 Oct 2026
- GHSA-mhh3-4wv2-rrj7SASL credentials are not redacted from `amqp10_client` crash dumps and `sys:get_status` outputMedium 5.7 25 Oct 2026
- GHSA-9h6g-46wc-m2f5Memory DoS via incomplete AMQP 0-9-1 messagesHigh 7.1 25 Oct 2026
- GHSA-j6hc-926v-qwq2RabbitMQ STOMP consumers retain OAuth queue access after JWT expirationMedium 4.9 18 Sept 2026
References
- GitHub Advisory Database https://github.com/advisories/GHSA-pj8f-mw2q-3xjj
- github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-pj8f-mw2q-3xjj