EUVD-2026-85655Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain monitoring-tag credentials
-
DeliveryReach federation-links management API
-
ExploitSend authenticated DELETE restart request
-
ExecutionFederation link restarts
-
ImpactMessage flow disrupted
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires all of: (1) the rabbitmq_federation AND rabbitmq_federation_management plugins enabled (non-default), (2) at least one active federation link to restart, and (3) attacker-held credentials carrying the monitoring tag. The flaw is the /federation-links/.../restart route authorizing via is_authorized_monitor while allowing the DELETE method with no per-method elevation check. Limiting factors: authentication is required (PR:L monitoring account), the impact is confined to availability of message flow (link restart), and the federation plugins are not enabled in default RabbitMQ installations - so exposure is restricted to broker deployments actively using federation. |
| Impact | This is a genuinely low-priority issue despite being a broken-access-control (CWE-862) flaw. All signals point to minor risk: the vendor CVSS 4.0 base is 2.3, driven entirely by VA:L (low availability impact) with VC:N/VI:N - no confidentiality or integrity loss. The vector requires an authenticated attacker (PR:L) who already holds a monitoring-tag account, and AT:P reflects that the rabbitmq_federation and rabbitmq_federation_management plugins must both be enabled (a non-default deployment condition). No EPSS score, no CISA KEV entry, and no public exploit code were provided, so exploitation status is 'no public exploit identified at time of analysis.' The only real-world impact is that a read-only monitoring user can trigger federation-link restarts that briefly disrupt message flow - a privilege-boundary violation rather than a system compromise. No signals conflict here; the low CVSS and absence of exploitation intelligence are mutually consistent. Note the input Tag 'Authentication Bypass' is inaccurate - this is an authorization/broken-access-control gap (monitoring tag lacks a per-method elevation check for DELETE), not an authentication bypass. |
| Exploit ScenarioDerived | An attacker with valid monitoring-tag credentials on a RabbitMQ node that has the federation plugins enabled sends an authenticated DELETE request to the /federation-links/.../restart management API route, which is guarded only by is_authorized_monitor. Because there is no per-method elevation check, the read-only user's request restarts an arbitrary federation link, interrupting inter-broker message replication. No public proof-of-concept was identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 23, 2026
Broken access control in the RabbitMQ management HTTP API lets a user holding only the monitoring tag restart any federation link via DELETE /api/federation-links/.../restart, an operation that should require elevated (management/policymaker/administrator) privileges - thereby disrupting message flow between federated brokers. Affected are RabbitMQ server releases prior to 3.13.15, 4.0.20, 4.1.11, 4.2.6, and 4.3.1, but only deployments that enable both the rabbitmq_federation and rabbitmq_federation_management plugins and have at least one active federation link. Exploitation requires an authenticated account carrying the monitoring tag (CVSS v4.0 PR:L), impact is limited to availability of the restarted link, the assessed severity is CVSS 2.3 / CVSS:3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L, and no public exploit code or confirmed in-the-wild exploitation was identified at time of analysis.
RemediationAI
Vendor-released patch: upgrade to RabbitMQ 3.13.15, 4.0.20, 4.1.11, 4.2.6, or 4.3.1 as applicable to your release branch (see GHSA-g5v3-w5xg-62q2 and the v4.2.6/v4.3.1 release tags). If immediate upgrade is not possible, apply compensating controls: remove the monitoring tag from any account that does not strictly need federation visibility, since that tag is the sole privilege required - the trade-off is loss of read-only monitoring access to federation status for those users; disable the rabbitmq_federation_management plugin (or disable federation entirely) on nodes that do not require link management, which removes the vulnerable route but sacrifices federation management/monitoring through the HTTP API; bind the management HTTP API to a trusted interface and restrict it with network ACLs or a reverse proxy so only administrative networks reach it, at the cost of convenience for remote operators; and treat monitoring-tagged credentials as sensitive, rotating them and preferring dedicated read-only accounts over shared ones. Note that authenticated users with management or administrator tags are not the intended exploit path here; the risk is specifically the elevation of monitoring-only principals to a state-changing action that can interrupt message flow between federated brokers.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 5 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a missing-authorization defect (CWE-862) in RabbitMQ's Erlang/OTP-based management HTTP API, which is served by the rabbitmq_management plugin and extended by rabbitmq_federation_management. The route /federation-links/{vhost}/{id}/restart performs its authorization decision using the monitoring-level check (is_authorized_monitor, satisfied by the 'monitoring' tag) while the route's allowed_methods permits DELETE, and delete_resource/2 is wired to rabbit_federation_link_sup:restart. Because there is no per-method elevation check requiring a privileged tag before the state-changing dispatch, and no code comment marking the read-only authorization as intentional, a monitoring-scoped principal can invoke a destructive operation. In effect the API conflates read visibility of federation link status with control over link lifecycle - the CPE cpe:2.3:a:rabbitmq:rabbitmq-server:*:*:*:*:*:*:*:* identifies rabbitmq-server as the affected package across the impacted release branches.
Know when Rabbitmq gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
Network-reachable management API, low complexity, but requires an authenticated monitoring account (PR:L); impact is limited to transient availability disruption of federated message flow (A:L), no confidentiality or integrity loss.
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
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.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
GitHub
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Sensitive credential disclosure in RabbitMQ affects installations running the management plugin with OAuth 2 configured
Pivotal RabbitMQ, versions 3.7.x prior to 3.7.21 and 3.8.x prior to 3.8.1, and RabbitMQ for Pivotal Platform, 1.16.x ver
Denial of service in the RabbitMQ Java client library (com.rabbitmq:amqp-client ≤ 5.30.0) allows a malicious or compromi
An issue was discovered in Pivotal RabbitMQ 3.x before 3.5.8 and 3.6.x before 3.6.6 and RabbitMQ for PCF 1.5.x before 1.
Parsing desynchronization in the RabbitMQ amqp091-go AMQP 0.9.1 client library before 1.13.0 lets a malicious or comprom
RabbitMQ's amqp091-go Go client library, in all versions before 1.13.0, builds TLS configuration from amqps:// URIs with
RabbitMQ is a multi-protocol messaging broker. Rated medium severity (CVSS 5.4), this vulnerability is remotely exploita
RabbitMQ brokers that use the OAuth2 plugin can silently fall back to disabled TLS certificate verification when no CA b
Silent AMQP 0.9.1 metadata corruption in the RabbitMQ amqp091-go Go client library prior to 1.13.0 lets an application t
TLS client-authentication bypass in the RabbitMQ trust-store plugin lets a remote unauthenticated attacker whose forged
TLS certificate validation is completely bypassed in the RabbitMQ Java client library (`com.rabbitmq:amqp-client`) prior
Denial of service in the official RabbitMQ Go client library amqp091-go (versions prior to 1.13.0): a malicious, comprom
Exploit-DB