CVE-2026-66075: CWE-862: Missing Authorization in rabbitmq rabbitmq-server
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.
AI Analysis
Technical Summary
RabbitMQ server versions prior to 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1 contain a missing authorization vulnerability (CWE-862) in the /federation-links/.../restart route. The is_authorized/2 function uses is_authorized_monitor, which accepts the monitoring tag, allowing users with monitoring privileges to perform DELETE operations that trigger federation link restarts via rabbit_federation_link_sup:restart. This bypasses intended authorization controls because there is no per-method elevation check, enabling read-only monitoring users to perform disruptive state-changing actions. The vulnerability requires the rabbitmq_federation and rabbitmq_federation_management plugins to be enabled. It is fixed in the versions listed above.
Potential Impact
An attacker with credentials having the monitoring tag can restart any federation link, disrupting message flow in RabbitMQ. This is a state-changing operation that should not be permitted for read-only monitoring users. The impact is limited to disruption of federation links and does not allow broader privilege escalation or data compromise. The CVSS 4.0 score is 2.3, indicating low severity.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1. Users should upgrade to these or later versions to remediate the issue. No additional mitigation is required if these versions are deployed.
CVE-2026-66075: CWE-862: Missing Authorization in rabbitmq rabbitmq-server
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 v4.0
Score 2.3low
Affected software
rabbitmq
rabbitmq-server
pkg:github/rabbitmq/rabbitmq-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ server versions prior to 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1 contain a missing authorization vulnerability (CWE-862) in the /federation-links/.../restart route. The is_authorized/2 function uses is_authorized_monitor, which accepts the monitoring tag, allowing users with monitoring privileges to perform DELETE operations that trigger federation link restarts via rabbit_federation_link_sup:restart. This bypasses intended authorization controls because there is no per-method elevation check, enabling read-only monitoring users to perform disruptive state-changing actions. The vulnerability requires the rabbitmq_federation and rabbitmq_federation_management plugins to be enabled. It is fixed in the versions listed above.
Potential Impact
An attacker with credentials having the monitoring tag can restart any federation link, disrupting message flow in RabbitMQ. This is a state-changing operation that should not be permitted for read-only monitoring users. The impact is limited to disruption of federation links and does not allow broader privilege escalation or data compromise. The CVSS 4.0 score is 2.3, indicating low severity.
Mitigation Recommendations
This vulnerability is fixed in rabbitmq-server versions 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1. Users should upgrade to these or later versions to remediate the issue. No additional mitigation is required if these versions are deployed.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-23T23:25:28.897Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab43b0df7a7c5410651755f
Added to database: 09/23/2026, 20:48:13 UTC
Last enriched: 09/23/2026, 21:03:23 UTC
Last updated: 09/24/2026, 03:12:22 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.