Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
8.7

CVE-2026-85724: Moquette broker lets unauthorized access and cause crash

CVE-2026-85724 · published 21 days ago
Summary

The Moquette MQTT broker (versions before 0.18.1) lets a client use special characters in its ID or username to expand permission rules, giving it the ability to read or write data belonging to other users. That same trick can also cause the broker to crash, interrupting service. Update the broker to version 0.18.1 or later to stop the unauthorized access and prevent crashes.

What to do
  • Update moquette io.moquette:moquette-broker to version 0.18.1.
  • Update io.moquette:moquette-broker to version 0.18.1.
  • Update moquette moquette to version 0.18.1 or later.
Affected software
Ecosystem VendorProductAffected versions
maven moquette io.moquette:moquette-broker <= 0.18.0
Fix: upgrade to 0.18.1
– moquette-io moquette < 0.18.1
maven – io.moquette:moquette-broker <= 0.18.0
Fix: upgrade to 0.18.1
– moquette moquette < 0.18.1
cpe:2.3:a:moquette:moquette:*:*:*:*:*:*:*:*
Maven – io.moquette:moquette-broker < 0.18.1
Fix: upgrade to 0.18.1
Original advisory text
Moquette: Pattern-ACL wildcard injection (cross-tenant authorization bypass) plus a remote-unauthenticated DoS cluster, a Will-message authorization bypass, and a cross-session durable-corruption bug
Moquette is a lightweight Java MQTT broker. Prior to 0.18.1, when pattern-based ACL rules are configured, AuthorizationsCollector.canDoOperation substitutes client ID and username values directly into rules containing %c or %u and then treats the result as an MQTT topic filter. A client that uses + or # in either identity can broaden the substituted filter and gain cross-tenant read and write access. A # identity can also produce an invalid filter that triggers a NullPointerException in Topic.match and disrupts session processing. This issue is fixed in version 0.18.1.
References
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker full control
Severity
8.7 High
Exploitation
<1% chance of attack within 30 days
Type
CWE-155Improper Neutralization of Wildcards or Matching Symbols
CWE-863Incorrect Authorization
CWE-99Improper Control of Resource Identifiers ('Resource Injection')
CWE-248Uncaught Exception
CWE-862Missing Authorization
CWE-636Not Failing Securely ('Failing Open')
CWE-770Allocation of Resources Without Limits
CWE-674Uncontrolled Recursion
CWE-20Improper Input Validation
Timeline
Published23 Sep 2026
Updated12 Oct 2026
First seen23 Sep 2026
Track software like this
Free during beta