Bug 2540090 - CVE-2026-66075 rabbitmq-server: RabbitMQ: Monitoring user can disrupt message flow via authorization flaw [fedora-all]
Summary: CVE-2026-66075 rabbitmq-server: RabbitMQ: Monitoring user can disrupt message...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: rabbitmq-server
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["0d336140-e777-4cde-a9a1-9...
Depends On:
Blocks: CVE-2026-66075
TreeView+ depends on / blocked
 
Reported: 2026-09-24 14:05 UTC by Jon Weiser
Modified: 2026-09-24 14:05 UTC (History)
2 users (show)

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


Attachments (Terms of Use)

Description Jon Weiser 2026-09-24 14:05:25 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 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.