Description
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.
Published: 2026-09-25
Score: 5.1 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Unauthorized MQTT topic access
Action: Apply patch
AI Analysis

Impact

The vulnerability arises from an incomplete escape routine used to construct MQTT topic permission expressions. The function escapes many regex metacharacters but omits the hyphen, allowing an attacker to insert a hyphen within a character class of a topic permission template. A low‑privileged authenticated MQTT user who controls the client identifier can craft a malicious identifier that expands the intended pattern, granting read or write access to MQTT topics that were not originally authorized. The flaw permits unauthorized topic access by manipulating permission templates, representing a breach of confidentiality and integrity for MQTT messages. Based on the description, the attack vector likely involves crafting a malicious client identifier through the MQTT connection.

Affected Systems

The affected product is RabbitMQ Server. Versions from 4.0.0 up to and including 4.3.3, 4.2.9, 4.1.14, and 4.0.23 contain the incomplete escape logic and are vulnerable. Versions 4.3.3, 4.2.9, 4.1.14, and 4.0.23 provide the fix.

Risk and Exploitability

The vulnerability carries a CVSS score of 5.1, indicating moderate severity. EPSS data is not available, and the flaw is not listed in the CISA KEV catalog. Exploitation requires a valid MQTT connection and a low‑privileged authenticated account; the attacker must control the client identifier. Since many environments allow MQTT for many users, the potential for exploitation is present, but lack of EPSS data suggests exploitation likelihood remains uncertain.

Generated by OpenCVE AI on September 25, 2026 at 18:25 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update RabbitMQ to any of the patched releases—4.3.3, 4.2.9, 4.1.14, or 4.0.23—to incorporate the complete escape logic.
  • If an upgrade cannot be performed immediately, disable the MQTT plugin for users who do not require MQTT functionality or limit its use to trusted accounts.
  • Review and modify topic permission templates to avoid placing client identifiers inside character classes, thereby preventing the escape bypass.

Generated by OpenCVE AI on September 25, 2026 at 18:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 26 Sep 2026 11:30:00 +0000

Type Values Removed Values Added
First Time appeared Rabbitmq
Rabbitmq rabbitmq-server
Vendors & Products Rabbitmq
Rabbitmq rabbitmq-server

Fri, 25 Sep 2026 18:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 25 Sep 2026 16:45:00 +0000

Type Values Removed Values Added
Description 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.
Title RabbitMQ: Incomplete fix for CVE-2026-44838: `escape_regex_char/1` does not escape `-`, leaving room for an MQTT topic permission bypass
Weaknesses CWE-862
References
Metrics cvssV4_0

{'score': 5.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:H/SA:N'}


Subscriptions

Rabbitmq Rabbitmq-server
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-09-25T17:20:31.333Z

Reserved: 2026-07-29T15:02:20.411Z

Link: CVE-2026-67407

cve-icon Vulnrichment

Updated: 2026-09-25T17:20:22.428Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-09-25T17:17:12.620

Modified: 2026-09-28T14:38:38.163

Link: CVE-2026-67407

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-26T11:15:10Z

Weaknesses