All vulnerabilities

Servers and applications

CVE-2026-67412

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

Severity
Medium 6.0
Published
23 Jul 2026
Last changed
18 Nov 2026
Added to UpHeron
1 Nov 2026
Fixed in
3.13.18, 4.0.23, 4.0.24, 4.1.14, 4.2.9, 4.3.3
Exploit chance
0.3% in the next 30 daysHigher than 18% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Missing authorization (CWE-862)
Attack
Over the network · Only under certain conditions · Needs a user account · No user action needed
Attacker can
Read data
CVSS vector
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
Also known as
GHSA-42pc-678q-v8qj
Sources
NVD, Project advisories (GitHub)

Description

  • 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 work. vhost isolation is RabbitMQ's tenancy boundary. policymaker is documented as scoped to "virtual hosts to which they can log in via AMQP", so reaching an unrelated vhost is outside that authority.
  • What is missing. When a federation-upstream URI is an empty-host ("direct") connection, the validator never checks the creating user against the vhost embedded in that URI.
  • How we know it is a mistake, not a design choice. RabbitMQ's own Shovel plugin runs exactly this check on the same direct-connection primitive (check_vhost_access on the URI's vhost). Federation's equivalent validator skips it.
  • Where it was reproduced.
From rabbitmq/rabbitmq-server's security advisory. Shortened; the full text is there.

Affected software

SoftwareAffected versions
RabbitMQServers and applications · cpe:a:broadcom:rabbitmq_server
  • From 3.13.0 before 3.13.18
  • From 4.0.0 before 4.0.24
  • From 4.1.0 before 4.1.14
  • From 4.2.0 before 4.2.9
  • From 4.3.0 before 4.3.3
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server
  • From 3.13.0 before 3.13.18
  • From 4.0.0 before 4.0.23
  • From 4.1.0 before 4.1.14
  • From 4.2.0 before 4.2.9
  • From 4.3.0 before 4.3.3

About RabbitMQ

open source message broker, sometimes referred to as "Rabbit"

From Wikidata, CC0 1.0.
Docker Hub pulls
3,918,841,187Docker Hub, 15 Nov 2026
GitHub stars
13,973GitHub, 15 Nov 2026
Forks
4,032GitHub, 15 Nov 2026
Latest release
v4.4.0GitHub, 15 Nov 2026
Released
19 Oct 2026GitHub
Developer
Jean-Sébastien PédronWikidata
License
Mozilla Public License, version 2.0Wikidata
Written in
ErlangWikidata
First published on GitHub
20 Sept 2010GitHub

Release lines

ReleaseLatestSecurity fixes
4.44.4.0Until 31 Jul 2027
4.34.3.7Until 31 Jan 2027
4.24.2.9Ended 31 Jul 2026
4.14.1.8Ended 30 Jan 2026
4.04.0.9Ended 30 Apr 2025
3.133.13.7Ended 30 Sept 2024

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-67412
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-67412
  • GitHub Advisory Database https://github.com/advisories/GHSA-42pc-678q-v8qj
  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-42pc-678q-v8qj