Is CVE-2026-67229 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-67229 being exploited in the wild.

How severe is CVE-2026-67229?

Informational severity, published 23 September 2026.

Which products and versions are affected?

VMware RabbitMQ before 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.

Is there a fix for CVE-2026-67229?

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-67229 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-67229?

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.

CVE-2026-67229: RabbitMQ denial of service in vhost metadata import

CVE-2026-67229 · Severity: info · Published 2026-09-23

RabbitMQ is a messaging broker used to route and manage application messages. An administrator importing a crafted configuration file can crash the RabbitMQ node by exhausting its atom table—a finite resource in Erlang—with millions of unique metadata keys. This results in a denial of service that stops message processing until the node is restarted.

Technologies: VMware RabbitMQ. Vendors: VMware.

Quick answers

Is CVE-2026-67229 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67229 being exploited in the wild.
How severe is CVE-2026-67229?: Informational severity, published 23 September 2026.
Which products and versions are affected?: VMware RabbitMQ before 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0.
Is there a fix for CVE-2026-67229?: 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-67229 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-67229?: 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 exists in the add_vhost/2 function which unsafely calls rabbit_data_coercion:atomize_keys/1 using binary_to_atom on vhost metadata, allowing arbitrary atom creation. An attacker with administrator credentials can upload a definitions file containing ~1M unique metadata keys (fitting within the 20 MB management body limit) to exhaust the atom table and crash the node. This is a local, authenticated denial of service requiring administrative access to the management API.

Affected products

VMware RabbitMQ before 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0

Timeline

2026-09-23: disclosed

References

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