Skip to main content
VulnerabilityPublished Updated

CVE-2026-85058: moquette · Missing Authorization

Affects moquetteSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 0.18.1 soon.

Data as of 2 Nov 2026, 22:58 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.18.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Upgrade moquette and io.moquette/moquette to 0.18.1.

Affected software

ProductAffectedFixed in
moquette-iomoquetteAffected
  • <0.18.1
Fixed in
  • 0.18.1
Mavenio.moquette/moquettepkg:maven/io.moquette/moquetteOther threatsAffected
  • <0.18.1
Fixed in
  • 0.18.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade moquette to version 0.18.1 or later, where this missing authorization vulnerability is fixed. No other mitigation is required as the fix addresses the root cause.

Description

Moquette is a lightweight Java MQTT broker. Prior to 0.18.1, PostOffice.publishWill publishes a client-controlled Last Will message through publish2Subscribers without invoking the authorizator.canWrite check used by normal PUBLISH paths. When anonymous access is enabled and topic ACLs restrict writes, a remote client can set an ACL-protected topic as the Last Will Topic during CONNECT and perform an abnormal client disconnect, causing the broker to inject attacker-controlled messages into a topic for which the client lacks write permission. This issue is fixed in version 0.18.1.

References

Community reviews

Loading reviews…