CVEvulnerability

CVE-2026-66075

2.3 LOW Published 2026-09-23 Modified 2026-10-19 Official page ↗
Status
Analyzed
Published
2026-09-23
Last modified
2026-10-19
Assigner
[email protected]
CVSS 4.0 ([email protected])
2.3 LOW — 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
CVSS 3.1 ([email protected])
5.4 MEDIUM — CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Weaknesses
CWE-862

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.

Affected configurations

• broadcom rabbitmq server (>= 3.13.0 < 3.13.15) • broadcom rabbitmq server (>= 4.0.0 < 4.0.20) • broadcom rabbitmq server (>= 4.1.0 < 4.1.11) • broadcom rabbitmq server (>= 4.2.0 < 4.2.6) • broadcom rabbitmq server (>= 4.3.0 < 4.3.1)

Related

Weakness · CWE (1)

  • CWE-862 Missing Authorization weakness

References