CVE-2026-67407: RabbitMQ is a messaging and streaming broker.
High CVSS 7.1
- CVE id
- CVE-2026-67407
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| RabbitMQ Runtimes and servers |
>= 4.0.0, < 4.0.23 >= 4.1.0, < 4.1.14 >= 4.2.0, < 4.2.9 >= 4.3.0, < 4.3.3 |
4.0.23, 4.1.14, 4.2.9, 4.3.3 |
How to fix it
Upgrade RabbitMQ to the fixed release of the line you run: 4.0.23, 4.1.14, 4.2.9, 4.3.3.
rabbitmqctl version
- Upgrade RabbitMQ (the rabbitmq image tag or the rabbitmq-server package) to the patched release, node by node.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
RabbitMQ is a messaging and streaming broker. From 4.0.0 until 4.3.3 and 4.2.9 and 4.1.14 and 4.0.23, Incomplete fix for CVE-2026-44838: escaperegexchar/1 does not escape -, leaving room for an MQTT topic permission bypass. the CVE-2026-44838 fix made expandtopicpermission/2 escape regex metacharacters in expanded topic-permission variables (escaperegex(V)), but escaperegexchar/1 escapes \ ^ $ . | ? + ( ) [ ] { } and omits -. When a topic permission template places {clientid} inside a [...] character class A low-privileged authenticated MQTT user controlling its clientid can broaden topic authorization (read and write) when templates embed {clientid} in a [...] This issue is fixed in versions 4.3.3 and 4.2.9 and 4.1.14 and 4.0.23.
References
- CVE-2026-67407 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-67407
- Web: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.2.9
- Web: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.3
- Web: https://github.com/rabbitmq/rabbitmq-server/security/advisories/GHSA-q46v-hrvq-hp24
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.