Privilege Escalation in RabbitMQ Federation Link Restart

Publication date: 2026-09-23

Last updated on: 2026-09-23

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-23

Last Modified

2026-09-23

Generated

2026-09-24

AI Q&A

2026-09-24

EPSS Evaluated

N/A

NVD

CVE-2026-66075

Affected Vendors & Products

Vendor	Product	Version / Range
rabbitmq	rabbitmq	to 4.3.1 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-862	The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

Executive Summary

This vulnerability in RabbitMQ allows a read-only monitoring user to restart federation links, which are state-changing operations that disrupt message flow. The issue occurs because the is_authorized/2 function for the /federation-links/.../restart route uses a monitoring tag instead of requiring elevated permissions. Affected versions are below 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1.

Impact Analysis

An attacker with monitoring credentials could restart federation links, causing disruptions in message flow and potential data loss or service unavailability. This requires the rabbitmq_federation and rabbitmq_federation_management plugins to be enabled.

Mitigation Strategies

Upgrade RabbitMQ to versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, or 4.3.1 or later to fix the issue. Disable the rabbitmq_federation and rabbitmq_federation_management plugins if not needed. Review user permissions to ensure monitoring users do not have unnecessary privileges.

Hi! I’m here to help you understand CVE-2026-66075. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70