Not scored yet

CVE-2026-67407

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.

What this means for your business

    What to do

    1. 1Ask your IT team or provider whether any of your systems use the affected product.
    2. 2If you do, follow the vendor's guidance. No patch reference has been published yet.

    Fastnexa security experts

    Not sure if your company is exposed to CVE-2026-67407?

    Tell us where you run the affected software and a Fastnexa penetration tester will check whether this flaw, or others like it, can be used against your websites, apps and network.

    The full test is free for our first 10 founding clients until 31 December 2026. See the offer

    Book a 30-min callWhatsApp us

    Think you’ve already been hit? Don’t wait on a form: call or WhatsApp +1 (732) 454 2616. We reply within 1 hour, 24/7. Emergency help →

    Scoring

    CVSS
    Not yet scored
    CVSS v4
    5.1
    Weakness
    CWE-862
    Assigned by
    security-advisories@github.com

    Dates

    Published
    2026-09-25
    Last modified
    2026-09-28
    Sources
    NVD

    References

    CVE-2026-67407 | CyberBrief