Bug 2540084

Summary:	CVE-2026-66069 rabbitmq-server: RabbitMQ: Monitoring user can reset authentication attempt counters [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Jon Weiser <jweiser>
Component:	rabbitmq-server	Assignee:	Peter Lemenkov <lemenkov>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	lemenkov, rjones
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["aaa8e545-9f95-4258-b438-8e273eaf2733"]}
Fixed In Version:	rabbitmq-server-4.3.6-1.fc46 rabbitmq-server-4.3.6-1.fc45 rabbitmq-server-4.2.9-2.fc44	Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2026-10-09 15:43:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2539756

Description Jon Weiser 2026-09-24 14:04:45 UTC

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.

Comment 1 Peter Lemenkov 2026-10-09 13:24:15 UTC

This issue is already fixed upstream in RabbitMQ 4.3.6, which is the version currently built for Fedora rawhide (rabbitmq-server-4.3.6-1.fc46) and Fedora 45 (rabbitmq-server-4.3.6-1.fc45).

Fedora 44 (currently 4.2.9) and Fedora 43 (currently 4.0.9) still need attention; backports/rebases for the still-supported stable branches are being worked on. Leaving this report open to track that remaining work.

Comment 2 Peter Lemenkov 2026-10-09 15:43:57 UTC

This issue is already addressed in the rabbitmq-server builds currently shipped in all maintained Fedora branches:

  * Fedora rawhide: rabbitmq-server-4.3.6-1.fc46
  * Fedora 45:      rabbitmq-server-4.3.6-1.fc45
  * Fedora 44:      rabbitmq-server-4.2.9-2.fc44

No new build is required for these branches, so closing as CURRENTRELEASE.

Fedora 43 (rabbitmq-server-4.0.9) will NOT be updated for this CVE batch: the upstream 4.0.x line ended at 4.0.9 (later 4.0.x fixes are commercial-only, with no public OSS release) and Fedora 43 reaches end of life on 2026-12-09, so a backport to F43 is not worthwhile.