Skip to main content
Vulnerability Database/CVE-2026-67412

CVE-2026-67412: RabbitMQ Auth Bypass Vulnerability

CVE-2026-67412 is an authentication bypass flaw in RabbitMQ that allows policymakers to read and drain messages from vhosts without proper authorization. This post covers technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-67412 Overview

CVE-2026-67412 is a missing authorization vulnerability [CWE-862] in RabbitMQ's Federation plugin. The flaw affects RabbitMQ versions from 3.13.0 up to the fixed releases 4.3.3, 4.2.9, 4.1.14, 4.0.24, and 3.13.18. Federation upstream configuration skips vhost authorization checks. A policymaker on one virtual host (vhost) can configure a federation upstream pointing at another vhost it has no permission on. With the default ack-mode, source messages are consumed and deleted rather than copied, breaking vhost tenancy boundaries.

Critical Impact

An authenticated low-privilege user with policy management rights on a single vhost can read and drain messages from other vhosts on the same cluster, violating multi-tenant isolation.

Affected Products

  • RabbitMQ Server 3.13.0 through 3.13.17
  • RabbitMQ Server 4.0.0 through 4.0.23, 4.1.0 through 4.1.13, 4.2.0 through 4.2.8
  • RabbitMQ Server 4.3.0 through 4.3.2 (Federation plugin enabled)

Discovery Timeline

  • 2026-09-25 - CVE-2026-67412 published to NVD
  • 2026-09-28 - Last updated in NVD database

Technical Details for CVE-2026-67412

Vulnerability Analysis

RabbitMQ's Federation plugin links brokers or vhosts so messages flow from an upstream source to a downstream destination. Federation upstreams are configured through parameters and activated via policies scoped to a vhost. The authorization gap allows a user with policy privileges on vhost-A to define a federation upstream whose URI points at vhost-B on the same cluster. The broker establishes the federation link using the credentials embedded in the upstream URI without re-validating that the policymaker has access to the target vhost.

Once the link is active, messages from queues in vhost-B are pulled into vhost-A. The default acknowledgment mode (on-confirm) causes consumed messages to be removed from the source queue rather than mirrored. This converts a confidentiality issue into a message-destruction and interception issue in the same operation.

Root Cause

The Federation plugin validates the upstream URI format and connection parameters but does not enforce vhost-level authorization for the invoking user against the target vhost. The missing check [CWE-862] breaks the tenancy model that vhosts are intended to provide.

Attack Vector

Exploitation requires network access to the management API or AMQP interface and valid credentials with policy and parameter configuration rights on at least one vhost. The attacker creates a federation upstream pointing to a target vhost queue, then applies a federation policy that matches the queue pattern. The broker begins draining messages from the target vhost into a queue the attacker controls. Refer to the GitHub Security Advisory GHSA-42pc-678q-v8qj for the full technical write-up.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-67412

Indicators of Compromise

  • Federation upstream parameters whose URI vhost component differs from the vhost in which the parameter is defined.
  • Unexpected federation links visible in rabbitmqctl list_federation_links targeting vhosts outside the operator's expected topology.
  • Sudden drop in queue depth on production vhosts with no corresponding consumer activity in local application logs.

Detection Strategies

  • Audit all federation parameters and policies across every vhost and compare the upstream URI vhost field against the hosting vhost.
  • Enable RabbitMQ audit logging for parameter and policy changes, then alert on new federation-upstream entries.
  • Correlate management API calls to /api/parameters/federation-upstream/* with the authenticated user and the targeted vhost.

Monitoring Recommendations

  • Track rabbitmq_federation_links metrics and alert when a link references a vhost outside its declared tenancy.
  • Ship RabbitMQ logs to a centralized analytics platform and flag parameter creation events from accounts without cluster-wide administrator roles.
  • Baseline message consumption rates per queue and alert on anomalous drain patterns during off-hours.

How to Mitigate CVE-2026-67412

Immediate Actions Required

  • Upgrade RabbitMQ to the first patched release on your supported line: 4.3.3, 4.2.9, 4.1.14, 4.0.24, or 3.13.18.
  • Enumerate all federation upstreams and policies cluster-wide and remove any that reference vhosts outside their defining tenancy.
  • Rotate credentials embedded in federation upstream URIs if they granted broader access than intended.

Patch Information

The fix is distributed in RabbitMQ Server v4.3.3 and RabbitMQ Server v4.2.9, plus the 4.1.14, 4.0.24, and 3.13.18 maintenance releases. The patched Federation plugin enforces vhost authorization for the invoking user when a federation upstream is created or updated.

Workarounds

  • Disable the Federation plugin on clusters that do not require cross-broker or cross-vhost replication using rabbitmq-plugins disable rabbitmq_federation.
  • Restrict policy and parameter configuration permissions so only trusted administrators can create federation upstreams.
  • Separate tenants onto distinct RabbitMQ clusters when strict message isolation is required and patching cannot be scheduled immediately.
bash
# Configuration example
# Disable the Federation plugin as a temporary workaround
rabbitmq-plugins disable rabbitmq_federation

# Review existing federation upstream parameters per vhost
rabbitmqctl list_parameters --vhost <vhost-name>

# Remove a suspicious upstream
rabbitmqctl clear_parameter --vhost <vhost-name> federation-upstream <upstream-name>

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.