Skip to main content
VulnerabilityPublished Updated

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

Affects rabbitmqSource GCVE Database

0
Compare
Authoritative record:CVE-2026-66069· Low 2.3

Not known to be exploited · CVSS 2.3 Low : upgrade to 4.2.7 or 4.1.13 when convenient.

Data as of 17 Nov 2026, 16:19 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.2.7, 4.1.13
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade rabbitmq to 4.2.7 or 4.1.13.

Affected software

ProductAffectedFixed in
Bitnamirabbitmqpkg:bitnami/rabbitmqOther threatsAffected
  • >=4.1.0 <4.1.13
  • >=4.2.0 <4.2.7
Fixed in
  • 4.1.13
  • 4.2.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in RabbitMQ versions 4.1.13, 4.2.7, and 4.3.0. Users should upgrade to these or later versions to remediate the issue. No additional mitigation is required if the system is updated. The Management plugin must be enabled and monitoring-tag privileges granted for the vulnerability to be exploitable.

Description

A vulnerability in RabbitMQ prior to versions 4.1.13, 4.2.7, and 4.3.0 allows a monitoring-tagged user to reset per-node authentication-attempt counters via a DELETE request to the /api/auth/attempts/:node endpoint. This action erases evidence of brute-force authentication attempts but does not affect logs. The issue arises because the DELETE operation does not require administrator privileges, unlike the analogous wm_reset endpoint. The vulnerability is fixed in versions 4.1.13, 4.2.7, and 4.3.0.

References

Community reviews

Loading reviews…