RabbitMQ, a messaging and streaming broker, had an authorization mismatch on the /federation-links/.../restart HTTP route. The is_authorized/2 check used the monitoring tag, which grants access to monitoring functions, but did not enforce a per‑method elevation check for the delete request that triggers the link restart. Consequently, a user with only the monitoring tag could restart any federation link, changing system state and interrupting message flow. This flaw is a CWE‑862 authorization bypass vulnerability.

The problem affects the rabbitmq-server product from the RabbitMQ vendor. All releases before 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1 are vulnerable. The issue is not present in the listed fixed versions. The vulnerability requires the rabbitmq_federation and rabbitmq_federation_management plugins to be enabled.

The CVSS score is 2.3, indicating a low severity. The EPSS score is not available, and the vulnerability is not listed in CISA's KEV catalog, meaning there is no evidence of widespread exploitation. An attacker must first gain authentic credentials that carry the monitoring tag and the federation plugins must be active; the vulnerability is then exploitable via the standard REST API. Because the operation is state‑changing, it can disrupt services, but the lack of privilege escalation keeps the threat surface limited.