CVE-2026-66069

published 23 Sep 2026 · updated 1 Nov 2026

RabbitMQ: Monitoring-tag DELETE of auth-attempt metrics

2.3LowCVSS 2.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
rabbitmq>=4.1.0 <4.1.13, >=4.2.0 <4.2.7

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-66069 severity on Zeptric[![CVE-2026-66069](https://zeptric.io/badge/cve/CVE-2026-66069.svg)](https://zeptric.io/cve/CVE-2026-66069)