Skip to content
Fencer Vulns
medium 5.4

CVE-2026-66075 json

RabbitMQ: Monitoring-tag user can restart federation links

published 2026-09-23 46 d ago modified 2026-10-20 19 d ago also BIT-rabbitmq-2026-66075 , EUVD-2026-85655 , GHSA-g5v3-w5xg-62q2

cvss
5.4
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami rabbitmq 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.1
  • vmware rabbitmq 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.1
  • pivotal_software rabbitmq 3.13.15, 4.0.20, 4.1.11, 4.2.6, 4.3.1
  • rabbitmq-server Debian 14 4.3.2-1

debian advisories DEBIAN-CVE-2026-66075

  • rabbitmq-server4.3 hummingbird 1 4.3.6-1.hum1

red hat advisories RHSA-2026:67552

  • rabbitmq-server Azure Linux 3.0 3.13.7-10

azure linux advisories AZL-105753

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-66075 updated cvss 4.3

rabbitmq-server: RabbitMQ: Monitoring user can disrupt message flow via authorization flaw

  • Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.2.hum1
    affected: workaround, no fix planned “Restrict monitoring access and disable federation management where it is not needed.”
  • Red Hat OpenStack Platform 18.0 rabbitmq-server
    affected: workaround, no fix available “Restrict monitoring access and disable federation management where it is not needed.”
  • Red Hat Hardened Images rabbitmq-server4.3 4.3.6-1.hum1
    fixed: vendor fix “Restrict monitoring access and disable federation management where it is not needed.” RHSA-2026:67552
  • Red Hat OpenStack Platform 13 (Queens) rabbitmq-server Red Hat OpenStack Platform 16.2 rabbitmq-server Red Hat OpenStack Platform 17.1 rabbitmq-server
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
45 d ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 4.0 2.3 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
CNA 4.0 2.3 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
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
OSV 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

Affected packages

ecosystem package affected fixed in
bitnami rabbitmq
>=3.13.0, <3.13.15
>=4.0.0, <4.0.20
>=4.1.0, <4.1.11
>=4.2.0, <4.2.6
>=4.3.0, <4.3.1
3.13.15
4.0.20
4.1.11
4.2.6
4.3.1

Affected products

  • rabbitmq rabbitmq-server

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.