All vulnerabilities

Servers and applications

CVE-2026-44838

RabbitMQ MQTT Topic Permission Authorization Bypass

Severity
Medium 5.3
Published
6 May 2026
Last changed
17 Nov 2026
Added to UpHeron
1 Nov 2026
Fixed in
3.13.13, 4.0.18, 4.1.9, 4.2.4
Exploit chance
0.2% in the next 30 daysHigher than 10% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Incorrect authorization (CWE-863)
Attack
Over the network · Only under certain conditions · Needs a user account · No user action needed
Attacker can
Read some data · Change some data · Slow it down
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:H/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-x866-xp2g-cx8v
Sources
NVD, Project advisories (GitHub)

Description

RabbitMQ's MQTT plugin allows for topic-level authorization using regular expressions with variable substitution. Administrators can create patterns such as ^{client_id}-sensors$ to restrict user access to topics that include their client ID. However, the client_id is provided by the user in the MQTT CONNECT packet and is inserted into the regex pattern without escaping special regex characters. This flaw enables an authenticated MQTT user to inject regex operators to bypass authorization.

For instance, a user with client_id="." can transform the pattern ^{client_id}-sensors$ into ^.-sensors$, which incorrectly matches any topic ending in -sensors.

Administrators can configure topic permissions using regular expressions that include variables like {client_id}. The intended behavior is to substitute this variable with the client's ID, thus restricting their access to a specific set of topics.

From rabbitmq/rabbitmq-server's security advisory. Shortened; the full text is there.

Workarounds

One of:

  • Disable the MQTT plugin
  • Do not use/rely on variable expansion in topic authorization
  • Switch to using separate users per client instead of topic authorization with extrapolated variables such as client_id
Workarounds as given by 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.4
RabbitMQServers and applications · github:rabbitmq/rabbitmq-server
  • From 3.13.0 before 3.13.13
  • From 4.0.0 before 4.0.18
  • From 4.1.0 before 4.1.9
  • From 4.2.0 before 4.2.4

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-44838
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-44838
  • GitHub Advisory Database https://github.com/advisories/GHSA-x866-xp2g-cx8v
  • github.com https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-x866-xp2g-cx8v