CVE-2026-67407: CWE-862: Missing Authorization in rabbitmq rabbitmq-server
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.
AI Analysis
Technical Summary
RabbitMQ versions 4.0.0 up to but not including 4.0.23, 4.1.0 up to but not including 4.1.14, 4.2.0 up to but not including 4.2.9, and 4.3.2 up to but not including 4.3.3 contain a missing authorization vulnerability (CWE-862) due to an incomplete fix for CVE-2026-44838. The function escaperegexchar/1 fails to escape the '-' character, which is significant when {clientid} is placed inside a [...] character class in MQTT topic permission templates. This allows a low-privileged authenticated MQTT user controlling their clientid to broaden topic authorization (read and write) beyond intended limits. The vulnerability is resolved in versions 4.0.23, 4.1.14, 4.2.9, and 4.3.3.
Potential Impact
An attacker with low-privileged authenticated MQTT access can bypass topic permission restrictions by exploiting improper escaping of regex metacharacters in topic permission templates. This leads to unauthorized read and write access to MQTT topics, potentially compromising message confidentiality and integrity within RabbitMQ deployments using affected versions.
Mitigation Recommendations
Upgrade rabbitmq-server to version 4.3.3, 4.2.9, 4.1.14, or 4.0.23 or later, where this issue is fixed. No other mitigation or workaround is indicated. Patch status is confirmed fixed in these versions.
CVE-2026-67407: CWE-862: Missing Authorization in rabbitmq rabbitmq-server
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.
CVSS v4.0
Score 5.1medium
Affected software
rabbitmq
rabbitmq-server
pkg:github/rabbitmq/rabbitmq-serverRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
RabbitMQ versions 4.0.0 up to but not including 4.0.23, 4.1.0 up to but not including 4.1.14, 4.2.0 up to but not including 4.2.9, and 4.3.2 up to but not including 4.3.3 contain a missing authorization vulnerability (CWE-862) due to an incomplete fix for CVE-2026-44838. The function escaperegexchar/1 fails to escape the '-' character, which is significant when {clientid} is placed inside a [...] character class in MQTT topic permission templates. This allows a low-privileged authenticated MQTT user controlling their clientid to broaden topic authorization (read and write) beyond intended limits. The vulnerability is resolved in versions 4.0.23, 4.1.14, 4.2.9, and 4.3.3.
Potential Impact
An attacker with low-privileged authenticated MQTT access can bypass topic permission restrictions by exploiting improper escaping of regex metacharacters in topic permission templates. This leads to unauthorized read and write access to MQTT topics, potentially compromising message confidentiality and integrity within RabbitMQ deployments using affected versions.
Mitigation Recommendations
Upgrade rabbitmq-server to version 4.3.3, 4.2.9, 4.1.14, or 4.0.23 or later, where this issue is fixed. No other mitigation or workaround is indicated. Patch status is confirmed fixed in these versions.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-29T15:02:20.411Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6ab6a5d5f7a7c54106055641
Added to database: 09/25/2026, 16:48:21 UTC
Last enriched: 09/25/2026, 17:03:29 UTC
Last updated: 09/26/2026, 02:45:01 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.