ReconXWatchtower

Where this stands

First reported 17/11/2026 18:39

  1. 1Unconfirmednot observed
  2. 2Corroborated18/11/2026 12:57BSI CERT-Bund (WID)
  3. 3Confirmed now18/11/2026 12:57BSI CERT-Bund (WID)
  4. 4Exploitednot yet

Unconfirmed was never seen on its own: the first report we had was already stronger.

Mosquitto: critical websockets remote code execution (CVE-2026-110486) and six other flaws; upgrade to 2.1.4

Eclipse Mosquitto · Critical (CVSS 9.8)Fix available

≥38,700internet-facing systems run Eclipse MosquittoShodan · at least · 19/11/2026

CVE-2026-110486 CVE-2026-126706 CVE-2026-126708 CVE-2026-126763 CVE-2026-129149 CVE-2026-129705 CVE-2026-130491

Published 18/11/2026 13:18

Timeline

4 events over 18 h

  1. 17/11/2026 18:39First report+18 h
  2. 18/11/2026 12:57CorroboratedBSI CERT-Bund (WID)+0 min
  3. 18/11/2026 12:57ConfirmedBSI CERT-Bund (WID)+21 min
  4. 18/11/2026 13:18Published on WatchtowerPro CISO

In short

An attacker who can reach a Mosquitto websockets listener that uses the built-in websockets implementation can run code on the broker before logging in, according to the maintainer's advisory. Versions 2.1.0 to 2.1.2 are affected. Six other flaws were published the same day. Upgrade to 2.1.4, or stop using websockets listeners or build with libwebsockets support. Shodan recognises at least 38,679 internet-facing Mosquitto servers worldwide, 7,751 of them in the EU (19/11/2026); the real number is likely higher, and how many run an affected version is not yet known.

How bad is it

Critical: an attacker who can reach a built-in websockets listener on Mosquitto 2.1.0 to 2.1.2 can run code before logging in (CVE-2026-110486).

Confirmed by the vendor or a CERT - no exploitation reported yet.

Severity score

9.8of 10Critical

The worst of 7 CVEs · CVSS 3.1 from NVD, from eclipse.org, read 19/11/2026. CVE-2026-126706, CVE-2026-126708, CVE-2026-126763, CVE-2026-129149, CVE-2026-129705, CVE-2026-130491: no score published yet.

What an attacker needs

  • Internet access to itEnough
  • A loginNot needed
  • A user to clickNo
  • Special settingsNo

Red helps the attacker, blue holds them back, grey is not published yet.

If it works, an attacker can

  • Read the data it holds
  • Change or delete that data
  • Take it offline

Type: denial of service.

A score is the worst case for the flaw, not a verdict on any one system. How we score · ReconX customers see which of their own systems are affected.

Affected versions

  • CVE-2026-110486 (websockets remote code execution): Mosquitto 2.1.0 to 2.1.2 inclusive, built-in websockets implementation.
  • CVE-2026-126708 and CVE-2026-126763: 2.0.0 to 2.0.22 and 2.1.0 to 2.1.2 inclusive.
  • CVE-2026-130491 (libmosquitto Will payload): 1.5 to 2.0.22 and 2.1.0 to 2.1.2 inclusive.
  • CVE-2026-129149, CVE-2026-126706 (mosquitto_ctrl) and CVE-2026-129705 (PROXY v2 listeners): 2.1.0 to 2.1.2 inclusive.
  • Builds compiled with libwebsockets support are not affected by CVE-2026-110486, according to the advisory's mitigation advice.

Fixed in

  • Mosquitto 2.1.4 is named by the maintainer as the upgrade for the websockets remote code execution flaw (CVE-2026-110486). The signals do not state fixed versions for the other six CVEs.

What to do now

  • Upgrade Mosquitto to 2.1.4 or later, especially if a websockets listener is reachable from untrusted networks.
  • If you cannot upgrade yet, stop using websockets listeners or use a build compiled with libwebsockets support.
  • Limit network access to Mosquitto listeners to trusted clients.
  • Only use mosquitto_ctrl against brokers you trust.
  • Put PROXY v2 listeners behind trusted proxies only and block other direct access.
  • Check the Mosquitto security advisories for fixes for the other CVEs, since the signals name no fixed versions for them. If you use OpenSSL 4.0 with FIPS and password files, check the advisory for CVE-2026-126708.

ReconX customers see the full notice - and their own systems

Our customers are alerted at every phase. Until a patch exists, the ReconX agent watches their servers from the inside for anomalies, and our outside view - the attacker's view - shows which systems to fix first.

In ReconX: the full analysis, 4 open questions, followed up as sources answer and all 8 sources with their dates. And technology matching: which of your systems run Eclipse Mosquitto, at which version, fixed or not - and what each one needs.

Sign in to ReconXAbout ReconX

Main sources

[NEU] [hoch] Eclipse Mosquitto: Mehrere Schwachstellen CERT · CVE-2026-110486: Eclipse Mosquitto: Remote code execution via websockets listeners Research · CVE-2026-126706: Eclipse Mosquitto: mosquitto_ctrl crashes when connecting to a hostile broker Research

Data: Shodan - Mosquitto (estimate, 19/11/2026)

← All Watchtower notices

Pro CISO publishes ReconX Watchtower notices from public sources so organisations can act early. A notice describes an issue, never any organisation's systems. Times are Amsterdam time. Report a vulnerability in our systems.

ReconX Watchtower opened to the public on 24 October 2026, in the wake of PHP2Shell - our contribution to a safer digital ecosystem.