Servers and applications
GHSA-6chv-gv3h-cvcj
RabbitMQ direct reply-to: forged suffix fanout causes quadratic mailbox memory
- Severity
- Medium 6.0
- Published
- 18 Aug 2026
- Last changed
- 18 Aug 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 4.2.10, 4.3.5
- Attack
- Over the network · Only under certain conditions · Needs a user account · No user action needed
- Attacker can
- Take it down
- CVSS vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N- Sources
- Project advisories (GitHub)
Description
RabbitMQ direct reply-to addresses have the form:
When resolving a destination, RabbitMQ decodes and validates the PID but discards the capability-key suffix. An attacker who obtains their own valid direct reply-to address can create many distinct routing keys that preserve the encoded PID and replace only the suffix.
A single message can carry these names through the AMQP CC header. RabbitMQ creates one volatile target per distinct name and sends one cast per target to the same channel/session PID. Every cast retains a copy of the message's full O(N) routing-key structure, producing N × O(N) = O(N²) mailbox memory.
The final capability-key check happens only after each cast reaches the target mailbox, too late to prevent amplification.
- The attacker has an authenticated AMQP account.
- The account can write to the default exchange.
- The attacker activates direct reply-to and obtains its own generated reply address. No victim address or cross-user information leak is required.
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-6chv-gv3h-cvcj
- github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-6chv-gv3h-cvcj