BIT-rabbitmq-2026-66069
See a problem?- Import Source
- https://github.com/bitnami/vulndb/tree/main/data/rabbitmq/BIT-rabbitmq-2026-66069.json
- JSON Data
- https://api.osv.dev/v1/vulns/BIT-rabbitmq-2026-66069
- Aliases
-
- CVE-2026-66069
- GHSA-fhwq-9rvh-prj2
- Published
- 2026-10-01T09:32:44Z
- Modified
- 2026-10-01T10:10:47Z
- Summary
- RabbitMQ: Monitoring-tag DELETE of auth-attempt metrics
- Details
-
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.
- Database specific
{ "cpes": [ "cpe:2.3:a:vmware:rabbitmq:*:*:*:*:*:*:*:*" ], "severity": "Low" }- References
Affected packages
Bitnami / rabbitmq
Package
- Name
- rabbitmq
- Purl
- pkg:bitnami/rabbitmq
Severity
- 2.3 (Low) CVSS_V4 - 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 CVSS Calculator