RabbitMQ rabbitmq-server
RabbitMQ: Incomplete fix for CVE-2026-44838: `escape_regex_char/1` does not escape `-`, leaving room for an MQTT topic permission bypass
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.3.2, < 4.3.3
- >= 4.2.0, < 4.2.9
- >= 4.1.0, < 4.1.14
- >= 4.0.0, < 4.0.23
Fixed in 4.3.3, 4.2.9, 4.1.14, 4.0.23
Mitigation
Upgrade rabbitmq-server to 4.3.3 or 4.2.9 or 4.1.14 or 4.0.23 or later.
References
- Vendor advisory github.com/rabbitmq/rabbitmq-server/security/a…
- Release notes github.com/rabbitmq/rabbitmq-server/releases/t…
- Release notes github.com/rabbitmq/rabbitmq-server/releases/t…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.