Quick answers
- Is CVE-2026-67412 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67412 being exploited in the wild.
- How severe is CVE-2026-67412?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- VMware RabbitMQ 3.13.0 to 3.13.17, 4.0.0 to 4.0.23, 4.1.0 to 4.1.13, 4.2.0 to 4.2.8, 4.3.0 to 4.3.2.
- Is there a fix for CVE-2026-67412?
- A patch was published on 2026-07-20: Fix released in versions 3.13.18, 4.0.24, 4.1.14, 4.2.9, 4.3.3 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-67412 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-67412?
- 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 Federation upstream feature in RabbitMQ fails to validate virtual host authorization when processing upstream URIs, allowing a principal with policy configuration rights on one vhost to access and drain messages from other vhosts. An attacker with vhost-level policy permissions can invoke federation without proper access control, reading or consuming messages across vhost boundaries. The vulnerability is fixed in patched versions.
Affected products
- VMware RabbitMQ 3.13.0 to 3.13.17, 4.0.0 to 4.0.23, 4.1.0 to 4.1.13, 4.2.0 to 4.2.8, 4.3.0 to 4.3.2
Timeline
- 2026-09-25: disclosed
- 2026-07-20: patched: Fix released in versions 3.13.18, 4.0.24, 4.1.14, 4.2.9, 4.3.3