Skip to main content
VulnerabilityPublished

CVE-2026-95847: moquette · Resource Injection

Affects moquetteSource CVE Database V5

0
Compare

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

Data as of 6 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.18.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 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 7 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 vulnerability is fixed. No other mitigation is indicated or required according to the available data.

Description

Moquette is a lightweight Java MQTT broker. Prior to 0.18.1, H2PersistentQueue derives a session's message-map name as queue_ plus the client ID and its metadata-map name as queue_ plus the client ID plus _meta. A durable session whose client ID ends in _meta can therefore make its message map collide with another client's metadata map. The colliding sessions read and write the same H2 MVStore map with incompatible value types, which can corrupt queue head and tail data and cause message loss, misdelivery, failed queue reloads, or exposure of queued content across sessions. This issue is fixed in version 0.18.1.

References

Community reviews

Loading reviews…