CVE-2026-67415

What it is

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.

At a glance

Exploitability

Can be exploited over the network with an admin-level account. High risk of service disruption.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-25 17:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-16 15:58 UTC Last updatedMost recent change to the record

Details

Published

2026-09-25 17:17 UTC

Last modified

2026-10-16 15:58 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-400 · Uncontrolled resource consumption

Record status

Analyzed

Affected

• Broadcom Rabbitmq Server < 4.2.9
• Broadcom Rabbitmq Server < 4.3.3

Attack profile CVSS 4.0 · 5.9

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

High

User interaction

None

Confidentiality

None

Integrity

None

Availability

High