Quick answers
- Is CVE-2026-67407 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-67407 being exploited in the wild.
- How severe is CVE-2026-67407?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- VMware RabbitMQ 4.0.0 to 4.0.22, 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-67407?
- 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-67407 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-67407?
- 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 escaperegexchar/1 function fails to escape the hyphen (-) character when constructing regex patterns for MQTT topic permissions, despite fixing other metacharacters for CVE-2026-44838. An authenticated attacker controlling their clientid can inject regex syntax when templates embed {clientid} inside a [...] character class, bypassing intended permission boundaries. Patches are available in versions 4.3.3, 4.2.9, 4.1.14, and 4.0.23.
Affected products
- VMware RabbitMQ 4.0.0 to 4.0.22, 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