Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-67415 Overview
CVE-2026-67415 is a resource exhaustion vulnerability [CWE-400] in RabbitMQ, an open-source messaging and streaming broker. The Shovel parameter parser converts attacker-controlled runtime parameter values into non-garbage-collected Erlang atoms before applying any bounds check or allowlist validation. An authenticated attacker with sufficient privileges can exhaust the node-wide atom table and crash the broker. Affected releases span versions 4.2.0 through 4.2.8 and 4.3.0 through 4.3.2. The maintainers released fixes in RabbitMQ 4.2.9 and 4.3.3.
Critical Impact
Malicious Shovel parameters are stored durably and reparsed on worker startup, so atom pressure recurs after a node restart even without a live attacker session.
Affected Products
- RabbitMQ Server versions 4.2.0 through 4.2.8
- RabbitMQ Server versions 4.3.0 through 4.3.2
- Deployments with the rabbitmq_shovel and rabbitmq_shovel_management plugins enabled
Discovery Timeline
- 2026-09-25 - CVE-2026-67415 published to the National Vulnerability Database
- 2026-09-28 - Last updated in NVD database
Technical Details for CVE-2026-67415
Vulnerability Analysis
The flaw resides in the Shovel plugin's runtime parameter parser. When an operator submits a Shovel parameter through the Management HTTP API, the parser converts attacker-supplied string values into Erlang atoms using unsafe atom creation. Erlang atoms are not garbage collected and the global atom table has a fixed upper bound, typically 1,048,576 entries per node.
The parser performs this conversion before validating input length or checking against a fixed allowlist of accepted values. An attacker who can create or update Shovel runtime parameters can inject many unique string values and allocate a new atom for each one. Once the atom table nears exhaustion, the Erlang virtual machine terminates the broker node.
Shovel runtime parameters are persisted to the broker's metadata store. On restart, workers reload each stored parameter and reparse the attacker-controlled values, recreating atoms and reproducing the denial-of-service condition without any new attacker interaction.
Root Cause
The root cause is the use of unsafe atom conversion on untrusted input in the Shovel parameter parser. Validation and allowlist enforcement occur after atom creation rather than before, so even rejected parameters consume atom table slots. This pattern maps to [CWE-400] uncontrolled resource consumption.
Attack Vector
Exploitation requires network reachability to the Management HTTP API and valid credentials assigned both the management and policymaker tags. The attacker must also hold permission to set Shovel runtime parameters on a target vhost, and both the rabbitmq_shovel and rabbitmq_shovel_management plugins must be enabled on the node.
Given these preconditions, the attacker issues repeated PUT requests to the /api/parameters/shovel/{vhost}/{name} endpoint, each with distinct string values in fields that are converted to atoms. Technical details are documented in the GitHub Security Advisory GHSA-8mpg-qw9r-m5cr.
Detection Methods for CVE-2026-67415
Indicators of Compromise
- High-volume PUT requests to /api/parameters/shovel/ endpoints from a single authenticated principal within a short interval.
- Unusually large numbers of Shovel runtime parameters configured on one or more vhosts.
- Erlang VM crash logs referencing system_limit or atom table exhaustion in rabbit.log.
- Repeated node restarts followed by renewed atom pressure consistent with reparsed persisted parameters.
Detection Strategies
- Query the Management HTTP API periodically with GET /api/parameters/shovel and alert on sudden growth in parameter count.
- Monitor the Erlang atom count on each node using erlang:system_info(atom_count) and compare against atom_limit.
- Correlate authentication logs for accounts holding the policymaker tag with Shovel parameter write operations.
Monitoring Recommendations
- Track atom table utilization as a time-series metric and alert when usage exceeds 70 percent of the configured limit.
- Forward RabbitMQ management audit logs to a centralized log platform for review of parameter CRUD operations.
- Baseline normal Shovel configuration churn per vhost and flag deviations.
How to Mitigate CVE-2026-67415
Immediate Actions Required
- Upgrade RabbitMQ to version 4.2.9 or 4.3.3, which contain the fix.
- Audit user accounts for unnecessary assignment of the management and policymaker tags and revoke where not required.
- Review existing Shovel runtime parameters on all vhosts and remove any suspicious or unknown entries before restarting nodes.
Patch Information
The RabbitMQ maintainers published fixed binaries in the RabbitMQ 4.2.9 release and the RabbitMQ 4.3.3 release. Both releases change the Shovel parameter parser to validate input against a fixed allowlist and enforce length bounds before any atom conversion occurs.
Workarounds
- Disable the rabbitmq_shovel and rabbitmq_shovel_management plugins on nodes that do not require Shovel functionality.
- Restrict network access to the Management HTTP API using firewall rules or a reverse proxy that limits source addresses to trusted operator networks.
- Remove the policymaker tag from accounts that do not need to manage runtime parameters.
# Disable the Shovel plugins where not required
rabbitmq-plugins disable rabbitmq_shovel_management
rabbitmq-plugins disable rabbitmq_shovel
# Remove the policymaker tag from an account that does not need it
rabbitmqctl set_user_tags <username> management
# Inspect existing Shovel runtime parameters prior to upgrade
rabbitmqctl list_parameters --vhost <vhost>
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

