What’s Vulnerable › Vulnerabilities

CVE-2026-66069: RabbitMQ: Monitoring-tag DELETE of auth-attempt metrics

• Severity: medium (CVSS 4.3 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.4% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-09-23 · updated 2026-10-30
• Weakness: CWE-862

Description

RabbitMQ is a messaging and streaming broker. Prior to versions 4.1.13, 4.2.7, and 4.3.0, is_authorized/2 uses is_authorized_monitor for all methods. DELETE resets rabbit_core_metrics:reset_auth_attempt_metrics(). Impact is cosmetic (counters only, no log erasure), but inconsistent with rabbit_mgmt_wm_reset.erl which requires admin for the analogous operation. A monitoring-tagged user can reset the per-node authentication-attempt counters via DELETE /api/auth/attempts/:node, erasing evidence of brute-force activity. The sibling endpoint wm_reset requires administrator. Preconditions include Management plugin enabled monitoring tag. This issue is fixed in versions 4.1.13, 4.2.7, and 4.3.0.

Affected products

• rabbitmq-server: from 4.1.0 before 4.1.13; from 4.2.0 before 4.2.7 — fixed in 4.1.13, 4.2.7
• rabbitmq-server: from 4.1.0, < 4.1.13; from 4.2.0, < 4.2.7

How to fix

Upgrade to a fixed version: rabbitmq-server 4.1.13, 4.2.7. Check the vendor advisory for mitigations.

References

• https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.7
• https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.0
• https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-fhwq-9rvh-prj2

Get alerted when CVE-2026-66069 or the next vulnerability affects your stack