Skip to content
Fencer Vulns
medium 4.3

CVE-2026-66069 json

RabbitMQ: Monitoring-tag DELETE of auth-attempt metrics

published 2026-09-23 46 d ago modified 2026-10-30 9 d ago also BIT-rabbitmq-2026-66069 , EUVD-2026-85632 , GHSA-fhwq-9rvh-prj2

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 23%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami rabbitmq 4.1.13, 4.2.7
  • vmware rabbitmq 4.1.13, 4.2.7
  • pivotal_software rabbitmq 4.1.13, 4.2.7
  • rabbitmq-server Debian 14 4.3.0-2

debian advisories DEBIAN-CVE-2026-66069

  • rabbitmq-server4.3 hummingbird 1 4.3.6-1.hum1

red hat advisories RHSA-2026:67552

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-66069 updated cvss 4.3

rabbitmq-server: RabbitMQ: Monitoring user can reset authentication attempt counters

  • Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.2.hum1
    affected: workaround, no fix planned “Restrict Management API access and monitoring-tag accounts, or disable the Management plugin where it is not needed.”
  • Red Hat OpenStack Platform 18.0 rabbitmq-server
    affected: workaround, no fix available “Restrict Management API access and monitoring-tag accounts, or disable the Management plugin where it is not needed.”
  • Red Hat Hardened Images rabbitmq-server4.3 4.3.6-1.hum1
    fixed: vendor fix “Restrict Management API access and monitoring-tag accounts, or disable the Management plugin where it is not needed.” RHSA-2026:67552
  • Red Hat OpenStack Platform 13 (Queens) rabbitmq-server Red Hat OpenStack Platform 16.2 rabbitmq-server Red Hat OpenStack Platform 17.1 rabbitmq-server
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
45 d ago

Exploit prediction

0.30% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 2.3 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
CNA 4.0 2.3 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami rabbitmq
>=4.1.0, <4.1.13
>=4.2.0, <4.2.7
4.1.13
4.2.7

Affected products

  • rabbitmq rabbitmq-server

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.