Bug 2539777 (CVE-2026-66075) - CVE-2026-66075 rabbitmq-server: RabbitMQ: Monitoring user can disrupt message flow via authorization flaw
Summary: CVE-2026-66075 rabbitmq-server: RabbitMQ: Monitoring user can disrupt message...
Keywords:
Status: NEW
Alias: CVE-2026-66075
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: 2540090
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-23 20:52 UTC by OSIDB Bzimport
Modified: 2026-09-24 14:05 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:52:06 UTC 
RabbitMQ is a messaging and streaming broker. Prior to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, is_authorized/2 for the /federation-links/.../restart route uses is_authorized_monitor (accepts the monitoring tag), while allowed_methods permits DELETE and delete_resource/2 triggers rabbit_federation_link_sup:restart. There is no per-method elevation check and no comment marking it intentional. A read-only monitoring user can restart any federation link , a state-changing operation that disrupts message flow. Preconditions include rabbitmq_federation + rabbitmq_federation_management plugins enabled Attacker has credentials with the monitoring tag. This issue is fixed in versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.
Note You need to log in before you can comment on or make changes to this bug.