CVE-2026-66069 RabbitMQ: Monitoring-tag DELETE of auth-attempt metrics
A monitoring-tagged user can reset authentication attempt counters, erasing brute-force evidence, due to missing authorization checks in the management API.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-66069?
CVE-2026-66069 is a low-severity missing authorization vulnerability in rabbitmq-server, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-862
Which versions are affected by CVE-2026-66069?
1 open source package ship an affected version, including rabbitmq.
| Package | Affected | Fixed in |
|---|---|---|
rabbitmq Bitnami | From 4.1.0 | 4.1.13, 4.2.7 |
How do I fix CVE-2026-66069?
Upgrade rabbitmq to a fixed version for your release line: 4.1.13 or 4.2.7.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-66069 being exploited?
There is no known exploitation of CVE-2026-66069 in the wild and no public exploit code.
Sources
Also known as AZL-105774, BIT-rabbitmq-2026-66069, DEBIAN-CVE-2026-66069, GHSA-fhwq-9rvh-prj2, UBUNTU-CVE-2026-66069.