Description
RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.9 and 4.3.3, the Shovel parameter parser converted attacker-controlled runtime parameter values into non-garbage-collected Erlang atoms before bounding them or checking a fixed allowlist. Exploitation requires network access to the Management HTTP API, valid credentials with both the management and policymaker tags, permission to set Shovel runtime parameters on a vhost, and the rabbitmq_shovel and rabbitmq_shovel_management plugins to be enabled. The attacker can exhaust the node-wide atom table and deny service, and malicious parameters are stored durably and reparsed when workers start, so atom pressure can recur after restart without a live attacker connection. This issue is fixed in versions 4.2.9 and 4.3.3.
Affected products
broadcom: rabbitmq server
References4
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-8m… Vendor AdvisoryExploitMitigation
- github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-8m… Vendor AdvisoryExploitMitigation
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9 Release Notes
- github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3 Release Notes
Metrics
- CVSS 3.1
-
4.9
MEDIUM
Score source: NVD
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H - CVSS 4.0
-
5.9
MEDIUM
Score source: CNA
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X - EPSS — exploit probability
- 0% percentile: 33 · as of 9 November 2026
- CWE
- CWE-400
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.