Skip to content
Fencer Vulns
high 7.1

CVE-2026-67412 json

RabbitMQ: Federation upstream skips vhost authorization allowing cross-vhost message access

published 2026-09-25 44 d ago modified 2026-10-09 30 d ago also BIT-rabbitmq-2026-67412 , EUVD-2026-87160 , GHSA-42pc-678q-v8qj

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

Summary

RabbitMQ is a messaging and streaming broker. From 3.13.0 until 4.3.3, 4.2.9 , 4.1.14, 4.0.24, and 3.13.18, Federation upstream in RabbitMQ skips vhost authorization allowing cross-vhost message access. what the bug lets you do. A policymaker on one vhost reads and drains messages out of another vhost it has no permission on. With the default ack-mode the source messages are consumed (deleted), not copied. Why that should not 1. Federation validates the upstream URI without any vhost-access Cross-vhost message read/drain from a per-vhost policymaker, breaking vhost tenancy This issue is fixed in versions 4.3.3, 4.2.9 , 4.1.14, 4.0.24, and 3.13.18.

Patch / fix

  • bitnami rabbitmq 3.13.18, 4.0.24, 4.1.14, 4.2.9, 4.3.3
  • pivotal_software rabbitmq 3.13.18, 4.0.24, 4.1.14, 4.2.9, 4.3.3
  • vmware rabbitmq 3.13.18, 4.0.24, 4.1.14, 4.2.9, 4.3.3
  • rabbitmq-server Debian 14 4.3.6-1

debian advisories DEBIAN-CVE-2026-67412

  • 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-105284

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-67412 updated cvss 6.5

rabbitmq-server: RabbitMQ: Unauthorized cross-vhost message access via missing Federation upstream authorization

  • Red Hat Hardened Images rabbitmq-server4.2 4.2.9-0.2.hum1
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 13 (Queens) rabbitmq-server Red Hat OpenStack Platform 16.2 rabbitmq-server Red Hat OpenStack Platform 17.1 rabbitmq-server
    affected: no fix planned “Out of support scope”
  • Red Hat OpenStack Platform 18.0 rabbitmq-server
    affected: no fix available “Fix deferred”
  • Red Hat Hardened Images rabbitmq-server4.3 4.3.6-1.hum1
    fixed: vendor fix RHSA-2026:67552

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
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
44 d ago

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-42pc-678q-v8qj referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 4.0 6.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N
CNA 4.0 6.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:L/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 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
OSV 3.1 7.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami rabbitmq
>=3.13.0, <3.13.18
>=4.0.0, <4.0.24
>=4.1.0, <4.1.14
>=4.2.0, <4.2.9
>=4.3.0, <4.3.3
3.13.18
4.0.24
4.1.14
4.2.9
4.3.3

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.