Quick answers
- Is CVE-2026-67415 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67415 being exploited in the wild.
- How severe is CVE-2026-67415?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- RabbitMQ 4.2.0 through 4.2.8, 4.3.0 through 4.3.2.
- Is there a fix for CVE-2026-67415?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-67415 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-67415?
- Check whether you run RabbitMQ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Shovel parameter parser in RabbitMQ 4.2.0–4.2.8 and 4.3.0–4.3.2 converts attacker-controlled runtime parameter values into Erlang atoms without prior bounds-checking or validation against an allowlist, leading to unbounded atom table growth. Exploitation requires network access to the Management HTTP API, valid credentials with management and policymaker tags, and the rabbitmq_shovel and rabbitmq_shovel_management plugins enabled. The vulnerability is fixed in versions 4.2.9 and 4.3.3.
Affected products
- RabbitMQ RabbitMQ 4.2.0 through 4.2.8, 4.3.0 through 4.3.2
Timeline
- 2026-09-25: disclosed