All reports
Medium

rabbitmq-server: rabbitmq-server: Denial of Service via Shovel plugin atom exhaustion

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-67415

Probability of exploitation in the next 30 days: 0.38%

FIRST EPSS · 2026-11-20

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.

A flaw was found in rabbitmq-server. An authenticated remote attacker with administrative privileges can cause a Denial of Service (DoS) by submitting crafted runtime parameters through the Shovel Management HTTP API. Because these parameters are converted into non-reclaimable memory identifiers (atoms) without validation, an attacker can exhaust system memory resources and crash the broker, causing persistent service failures that can recur across restarts.