Bug 2539756 (CVE-2026-66069) - CVE-2026-66069 rabbitmq-server: RabbitMQ: Monitoring user can reset authentication attempt counters
Summary: CVE-2026-66069 rabbitmq-server: RabbitMQ: Monitoring user can reset authentic...
Keywords:
Status: NEW
Alias: CVE-2026-66069
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2540084
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-23 20:32 UTC by OSIDB Bzimport
Modified: 2026-09-24 14:18 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-23 20:32:28 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.