WaratekVRT Sign in

CVE-2026-85058

Severity7.5 High CVSS 3.1
Fixed in0.18.1
WeaknessMissing authorization (CWE-862)
Published18 Sep 2026
Updated24 Sep 2026

Published 57 days ago. NVD often adds the list of affected products days or weeks after a CVE is published, and the other sources we check lag too. The scope and status here may change.

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.

Exploitation status

Proof of concept only

A proof of concept exists, but no reviewed exploit catalogue lists this CVE.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment exploitation: poc CISA recorded that an exploit has been demonstrated. Automatable: yes, technical impact: partial.
  • Indexed PoC none indexed
  • EPSS 0.57% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: moquette-io/moquette e23df01.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.
Candidate fix https://github.com/moquette-io/moquette/commit/e23df019f6a11e22c7d2047d4f86d07095466c97 : a commit: the change itself

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
io.moquette:moquette-broker 0 0.18.1 unbounded

Products and versions

1 product, 1 version entry
SourceVendorProductSchemeAffected versions
osv io.moquette moquette-broker generic < 0.18.1

References

URLTags
https://github.com/moquette-io/moquette/commit/e23df019f6a11e22c7d2047d4f86d07095466c97 commit
https://github.com/moquette-io/moquette/security/advisories/GHSA-9jjc-fw8x-fmwx WEB
https://github.com/moquette-io/moquette/commit/f5a323fe782d1505c0097498cb22eb6ec6c96973 WEB
https://github.com/moquette-io/moquette PACKAGE
https://github.com/moquette-io/moquette/releases/tag/v0.18.1 WEB

Timeline

Published2026-09-18By the CVE Program.
NVD record modified2026-09-24NVD's own last-modified date for this record.