Bug 2566811

Summary:	CVE-2026-67412 rabbitmq-server: RabbitMQ: Unauthorized cross-vhost message access via missing Federation upstream authorization [fedora-all]
Product:	[Fedora] Fedora	Reporter:	Mauro Matteo Cascella <mcascell>
Component:	rabbitmq-server	Assignee:	Peter Lemenkov <lemenkov>
Status:	ON_QA ---	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide	CC:	lemenkov, rich
Target Milestone:	---	Keywords:	Security, SecurityTracking
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	{"flaws": ["b3eecbc0-ee67-4ce3-b292-6fa14129dfae"]}
Fixed In Version:		Doc Type:	---
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	2541507

Description Mauro Matteo Cascella 2026-11-04 10:23:49 UTC

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.

Comment 1 Peter Lemenkov 2026-11-04 15:44:17 UTC

This issue is fixed upstream in RabbitMQ 4.2.9 and 4.3.3. Fedora 45 and rawhide ship rabbitmq-server-4.3.7, and Fedora 44 ships rabbitmq-server-4.2.9, so both are already fixed.

The Fedora 43 (4.0.9) status is still being evaluated.

Comment 2 Fedora Update System 2026-11-04 18:15:19 UTC

FEDORA-2026-ea1afc0a7b (rabbitmq-server-4.0.9-7.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-ea1afc0a7b

Comment 3 Fedora Update System 2026-11-05 16:09:08 UTC

FEDORA-2026-ea1afc0a7b has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-ea1afc0a7b`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-ea1afc0a7b

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.