CVE-2026-67241

Undergoing Analysis Undergoing Analysis - In Progress

AMQP 1.0 Alternate-Exchange Permission Bypass in RabbitMQ

Publication date: 2026-09-25

Last updated on: 2026-09-29

Assigner: GitHub, Inc.

Description

RabbitMQ is a messaging and streaming broker. From 4.2.0 until 4.2.9 and 4.3.3, AMQP 1.0 management exchange.declare skips alternate-exchange permission check. pUT /exchanges/:name (lines 192-240) checks only configure on the declared exchange and passes XArgs straight to rabbitexchange:declare/7. It omits the checkreadpermitted(X) + checkwritepermitted(AE) that rabbitchannel.erl:2540-2548 enforces for the alternate-exchange argument on the AMQP 0-9-1 path. The same file already implements the analogous DLX check for queues (lines 708-719), confirming this is a missing-check bug rather than intentional A user with only configure on exchange X can route X's unroutable messages into an alternate exchange they have no write permission AMQP 1.0 enabled (default in RabbitMQ 4.x) Attacker has configure on at least one exchange but lacks write on the target. This issue is fixed in versions 4.2.9 and 4.3.3.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-09-25

Last Modified

2026-09-29

Generated

2026-10-16

AI Q&A

2026-09-25

EPSS Evaluated

2026-10-14

NVD

CVE-2026-67241

EUVD

EUVD-2026-87153

Affected Vendors & Products

Vendor	Product	Version / Range
rabbitmq	rabbitmq	From 4.2.0 (inc) to 4.2.9 (inc)
rabbitmq	rabbitmq	4.3.3

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

This vulnerability in RabbitMQ (CVE-2026-67241) allows users with configure permissions on an exchange to route unroutable messages to an alternate exchange without having write permissions on that alternate exchange. The issue occurs in AMQP 1.0 where the alternate-exchange permission check is skipped during exchange declaration.

Detection Guidance

To detect this vulnerability, check RabbitMQ server versions between 4.2.0-4.2.8 and 4.3.0-4.3.2. Use commands like 'rabbitmqctl status' or 'rabbitmq-diagnostics status' to verify the version. If vulnerable, upgrade to 4.2.9 or 4.3.3 or later.

Impact Analysis

An attacker with configure permissions on at least one exchange but lacking write permissions on a target exchange could exploit this to redirect unroutable messages to that target exchange. This could lead to unauthorized message routing or potential data leakage if the alternate exchange is controlled by the attacker.

Compliance Impact

This vulnerability could potentially impact compliance with GDPR and HIPAA by allowing unauthorized data exfiltration. An attacker with configure permissions on an exchange could route unroutable messages to an alternate exchange without write permissions, potentially exposing sensitive data. This unauthorized access may violate data protection requirements under GDPR (e.g., unauthorized access to personal data) and HIPAA (e.g., unauthorized disclosure of protected health information).

Mitigation Strategies

Upgrade RabbitMQ to version 4.2.9 or 4.3.3 or later to address the missing alternate-exchange permission check in AMQP 1.0 management.

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

0/70