RabbitMQ up to 4.2.8/4.3.2 AMQP 1.0 Management Exchange rabbitchannel.erl rabbitexchange:declare alternate-exchange permission

Summaryinfo

A vulnerability has been found in RabbitMQ up to 4.2.8/4.3.2 and classified as very critical. Affected is the function rabbitexchange:declare of the file rabbitchannel.erl of the component AMQP 1.0 Management Exchange. Performing a manipulation of the argument alternate-exchange results in permission. This vulnerability was named CVE-2026-67241. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in RabbitMQ up to 4.2.8/4.3.2. It has been classified as very critical. This affects the function rabbitexchange:declare of the file rabbitchannel.erl of the component AMQP 1.0 Management Exchange. The manipulation of the argument alternate-exchange with an unknown input leads to a permission vulnerability. CWE is classifying the issue as CWE-275. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2026-67241 since 07/28/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/25/2026). The attack technique deployed by this issue is T1222 according to MITRE ATT&CK.

Upgrading to version 4.2.9 or 4.3.3 eliminates this vulnerability.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

• RabbitMQ

Version

• 4.2.0
• 4.2.1
• 4.2.2
• 4.2.3
• 4.2.4
• 4.2.5
• 4.2.6
• 4.2.7
• 4.2.8
• 4.3.0
• 4.3.1
• 4.3.2

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion