All vulnerabilities

Servers and applications

CVE-2026-67241

AMQP 1.0 management exchange.declare skips alternate-exchange permission check

Severity
Medium 4.8
Published
22 Jul 2026
Last changed
16 Oct 2026
Added to UpHeron
1 Nov 2026
Fixed in
4.0.23, 4.1.14, 4.2.9, 4.3.3
Exploit chance
0.4% in the next 30 daysHigher than 37% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Missing authorization (CWE-862)
Attack
Over the network · Only under certain conditions · Needs an administrator account · No user action needed
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:L/SI:H/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Also known as
GHSA-rg2g-289m-xhhw
Sources
NVD, Project advisories (GitHub)

Description

This vulnerability was identified by Team RabbitMQ and/or other teams at Broadcom, not via a responsible disclosure from an external researcher.

A user with only configure on exchange X can route X's unroutable messages into an alternate exchange they have no write permission on.

PUT /exchanges/:name (lines 192-240) checks only configure on the declared exchange and passes XArgs straight to rabbit_exchange:declare/7. It omits the check_read_permitted(X) + check_write_permitted(AE) that rabbit_channel.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 design.

  • AMQP 1.0 enabled (default in RabbitMQ 4.x)
  • Attacker has configure on at least one exchange but lacks write on the target alternate-exchange
From rabbitmq/rabbitmq-server's security advisory.

Affected software

SoftwareAffected versions
RabbitMQServers and applications · cpe:a:broadcom:rabbitmq_server
  • From 4.2.0 before 4.2.9
  • From 4.3.0 before 4.3.3
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server
  • From 4.0.0 before 4.0.23
  • From 4.1.0 before 4.1.14
  • From 4.2.0 before 4.2.9
  • From 4.3.0 before 4.3.3

About RabbitMQ

open source message broker, sometimes referred to as "Rabbit"

From Wikidata, CC0 1.0.
Docker Hub pulls
3,918,841,187Docker Hub, 15 Nov 2026
GitHub stars
13,973GitHub, 15 Nov 2026
Forks
4,032GitHub, 15 Nov 2026
Latest release
v4.4.0GitHub, 15 Nov 2026
Released
19 Oct 2026GitHub
Developer
Jean-Sébastien PédronWikidata
License
Mozilla Public License, version 2.0Wikidata
Written in
ErlangWikidata
First published on GitHub
20 Sept 2010GitHub

Release lines

ReleaseLatestSecurity fixes
4.44.4.0Until 31 Jul 2027
4.34.3.7Until 31 Jan 2027
4.24.2.9Ended 31 Jul 2026
4.14.1.8Ended 30 Jan 2026
4.04.0.9Ended 30 Apr 2025
3.133.13.7Ended 30 Sept 2024

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-67241
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-67241
  • GitHub Advisory Database https://github.com/advisories/GHSA-rg2g-289m-xhhw
  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-rg2g-289m-xhhw