CVE-2026-67226: RabbitMQ atom exhaustion in user tags management

CVE-2026-67226 · Severity: info · Published 2026-09-25

RabbitMQ is a message broker used to route and queue messages between applications. An administrator can crash a RabbitMQ node by creating a user with millions of unique tags through the management API, exploiting unbounded atom creation in the Erlang runtime. This denial of service requires administrator access but impacts the availability of the entire messaging system.

Technologies: VMware RabbitMQ. Vendors: VMware.

Quick answers

Is CVE-2026-67226 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-67226 being exploited in the wild.
How severe is CVE-2026-67226?
Informational severity, published 25 September 2026.
Which products and versions are affected?
VMware RabbitMQ 4.0.0 to 4.0.21, 4.1.0 to 4.1.13, 4.2.0 to 4.2.6.
Is there a fix for CVE-2026-67226?
A patch was published on 2026-09-25: Fixed in versions 4.0.22, 4.1.14, 4.2.7 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67226 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67226?
Check whether you run VMware 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 vulnerability is an atom exhaustion denial of service in the PUT /api/users endpoint where the settags/2 function maps rabbitdatacoercion:toatom/1 over user-supplied tags without limit. An attacker with admin credentials can send ~1M unique tag strings (fitting within the 20 MB body limit) to exhaust the fixed-size atom table and crash the node. The fix limits user tags to a reasonable maximum number.

Affected products

  • VMware RabbitMQ 4.0.0 to 4.0.21, 4.1.0 to 4.1.13, 4.2.0 to 4.2.6

Timeline

  • 2026-09-25: disclosed
  • 2026-09-25: patched: Fixed in versions 4.0.22, 4.1.14, 4.2.7

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.