Quick answers
- Is CVE-2026-67222 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67222 being exploited in the wild.
- How severe is CVE-2026-67222?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- VMware RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5.
- Is there a fix for CVE-2026-67222?
- A patch was published on 2026-09-25: Fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67222 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-67222?
- 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 mechanisms/1 function in amqp_client applies Erlang's list_to_atom/1 to every colon-delimited token in an attacker-controlled auth_mechanism value, permanently consuming VM atoms without cleanup. Exploitation requires network access, the Shovel or Federation plugin to be enabled, and the policymaker role to configure authentication policies. An attacker can crash the node in one to three requests by exceeding atom limits.
Affected products
- VMware RabbitMQ 3.13.0 to 3.13.14, 4.0.0 to 4.0.19, 4.1.0 to 4.1.10, 4.2.0 to 4.2.5
Timeline
- 2026-09-25: disclosed
- 2026-09-25: patched: Fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.0