Quick answers
- Is CVE-2026-66078 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66078 being exploited in the wild.
- How severe is CVE-2026-66078?
- Informational severity, published 25 September 2026.
- Which products and versions are affected?
- VMware RabbitMQ 3.13.0 to 3.13.14, 4.0.x before 4.0.20, 4.1.x before 4.1.11, 4.2.x before 4.2.6.
- Is there a fix for CVE-2026-66078?
- A patch was published on 2026-09-25: Fixed in 3.13.15, 4.0.20, 4.1.11, 4.2.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-66078 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-66078?
- 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 authorization bypass in the bulk-delete user endpoint (/api/users/bulk-delete) which fails to check the is_protected_user guard before deleting accounts. While the single-delete endpoint (DELETE /api/users/:name) correctly enforces the protected-tag check via the rabbitmgmtwmuser:deleteresource/2 function, the bulk endpoint bypasses this by calling rabbitauthbackendinternal:deleteuser/2 directly without the guard. An authenticated administrator can exploit this to silently delete protected-tagged users that should be immutable.
Affected products
- VMware RabbitMQ 3.13.0 to 3.13.14, 4.0.x before 4.0.20, 4.1.x before 4.1.11, 4.2.x before 4.2.6
Timeline
- 2026-09-25: disclosed
- 2026-09-25: patched: Fixed in 3.13.15, 4.0.20, 4.1.11, 4.2.6