Servers and applications
GHSA-3526-xvv4-q9mr
RabbitMQ administrator RCE through reflected Erlang distribution authentication
- Severity
- Medium 5.9
- Published
- 18 Aug 2026
- Last changed
- 18 Aug 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 3.13.19, 4.0.24, 4.1.15, 4.2.10, 4.3.5
- Attack
- Over the network · Only under certain conditions · Needs an administrator account · No user action needed
- Attacker can
- Read data · Change some data
- CVSS vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N- Sources
- Project advisories (GitHub)
Description
This advisory describes a complex attack that requires administrative access to the HTTP API and a number of other variables to hold true.
A RabbitMQ management user with the administrator tag can escalate from broker administration to arbitrary BEAM function execution without knowing the Erlang distribution cookie and without local operating-system access.
The chain combines three behaviors:
- Administrator-accessible global-parameter names are converted into new Erlang atoms. This lets the attacker intern two node names such as evil@attacker and oracle@attacker.
- DELETE /api/reset/:node accepts any existing node atom and performs rabbit:is_running(Node) before checking whether the node is a cluster member. Two concurrent requests initiate two outbound Erlang distribution handshakes to attacker-controlled nodes.
- OTP 27's legacy cookie digest is bound to the cookie and challenge but not the peer identity, connection direction, or complete transcript.
Workarounds
One of:
- Block traffic to the rarely used DELETE /api/reset/{node} HTTP APi endpoint
- Restrict port 4369 (epmd) and 25672 (used by RabbitMQ nodes, the value is the default) access only to the hosts that run RabbitMQ cluster members
- Disable the rabbitmq_management plugin and use Prometheus and Grafana plus CLI tools for monitoring
- Restrict EPMD and distribution egress to explicit cluster peers.
- Use mutually authenticated TLS distribution with strict peer verification.
- Restrict administrator credentials and monitor their use.
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-3526-xvv4-q9mr
- github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-3526-xvv4-q9mr