CVE-2026-67412

Analyzed Analyzed - Analysis Complete

Federation Cross-Vhost Message Access in RabbitMQ

Publication date: 2026-09-25

Last updated on: 2026-10-08

Assigner: GitHub, Inc.

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-25

Last Modified

2026-10-08

Generated

2026-10-17

AI Q&A

2026-09-25

EPSS Evaluated

2026-10-16

NVD

CVE-2026-67412

EUVD

EUVD-2026-87160

Affected Vendors & Products

Vendor	Product	Version / Range
broadcom	rabbitmq_server	From 4.0.0 (inc) to 4.0.24 (exc)
broadcom	rabbitmq_server	From 4.1.0 (inc) to 4.1.14 (exc)
broadcom	rabbitmq_server	From 4.2.0 (inc) to 4.2.9 (exc)
broadcom	rabbitmq_server	From 4.3.0 (inc) to 4.3.3 (exc)
broadcom	rabbitmq_server	From 3.13.0 (inc) to 3.13.18 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-862	The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

Executive Summary

RabbitMQ versions from 3.13.0 to 4.3.3, 4.2.9, 4.1.14, 4.0.24, and 3.13.18 have a vulnerability in Federation upstream where vhost authorization is skipped. This allows a policymaker on one virtual host to read and drain messages from another virtual host without permission. Messages are consumed (deleted) rather than copied, breaking vhost tenancy.

Detection Guidance

Detecting this vulnerability requires checking RabbitMQ versions and federation configurations. Verify if your RabbitMQ version is between 3.13.0 and 4.3.3 (exclusive) or 4.0.0 to 4.2.9 (exclusive), or 4.1.0 to 4.1.14 (exclusive). Use commands like 'rabbitmqctl status' or 'rabbitmq-diagnostics status' to check the version.

Impact Analysis

This vulnerability allows unauthorized access to messages across different virtual hosts. Attackers with access to one vhost could read or delete messages from another vhost they should not have access to, potentially leading to data leaks or loss of sensitive information.

Compliance Impact

This vulnerability could lead to unauthorized data access or loss, violating compliance requirements for data protection such as GDPR or HIPAA. It undermines tenant isolation and data segregation, which are critical for meeting regulatory standards.

Mitigation Strategies

Upgrade RabbitMQ to fixed versions: 4.3.3, 4.2.9, 4.1.14, 4.0.24, or 3.13.18. If upgrading is not immediately possible, review and restrict federation upstream configurations to prevent unauthorized cross-vhost access.

Hi! I’m here to help you understand CVE-2026-67412. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70