Quick answers
- Is CVE-2026-66075 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66075 being exploited in the wild.
- How severe is CVE-2026-66075?
- Informational severity, published 23 September 2026.
- Which products and versions are affected?
- RabbitMQ Before 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.1.
- Is there a fix for CVE-2026-66075?
- A patch was published on 2026-04-23: RabbitMQ 4.2.6 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-66075 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-66075?
- Check whether you run 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-links/.../restart endpoint uses is_authorized_monitor for permission checks (allowing the monitoring tag) but allowed_methods permits DELETE, triggering delete_resource/2 without per-method privilege elevation validation. An attacker with monitoring credentials can invoke the restart operation to disrupt federation links. The vulnerability requires rabbitmq_federation and rabbitmq_federation_management plugins to be enabled.
Affected products
- RabbitMQ RabbitMQ Before 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.1
Timeline
- 2026-09-23: disclosed
- 2026-04-23: patched: RabbitMQ 4.2.6 released
- 2026-05-20: patched: RabbitMQ 4.3.1 released