Skip to main content
VulnerabilityPublished

CVE-2026-95848: moquette · Failing Open

Affects moquetteSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.3 Critical : upgrade to 0.18.1 as a priority.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 4.0 base score
9.3Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 36% 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:H/VI:H/VA:N/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 moquette-io/moquette to 0.18.1.

Affected software

ProductAffectedFixed in
moquette-iomoquetteAffected
  • <0.18.1
Fixed in
  • 0.18.1
GitHubmoquette-io/moquettepkg:github/moquette-io/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 issue is fixed. Prior to upgrading, verify that authenticator and authorizator classes are correctly configured and loadable to avoid fallback to permissive defaults.

Description

Moquette is a lightweight Java MQTT broker. Prior to 0.18.1, when a configured authenticator or authorizator class cannot be loaded, Server.initializeAuthenticator and Server.initializeAuthorizatorPolicy treat the failure as though no custom class was configured and fall back to AcceptAllAuthenticator or PermitAllAuthorizatorPolicy. A misspelled class name, missing dependency, constructor failure, or classpath problem can therefore start the broker with authentication or authorization disabled even though the operator configured those controls. This issue is fixed in version 0.18.1.

References

Community reviews

Loading reviews…