CVE-2026-110486
Eclipse Mosquitto 2.1 brokers with a WebSocket listener can be taken over before login; upgrade to 2.1.4
Reachable if a Mosquitto 2.1.0 to 2.1.2 broker built with its built-in WebSocket support has a protocol websockets listener that an attacker can reach over the network. No credentials are needed, since the CVE record says the bug triggers before authentication
Skip 2.1.3 and go straight to 2.1.4. CVE-2026-110486 lets anyone who can reach a Mosquitto 2.1 WebSocket listener corrupt the broker's memory before logging in, and Eclipse says it can lead to remote code execution. Version 2.1.3 fixed the flaw but broke legacy sha512 passwords, which Eclipse fixed in 2.1.4 the same day. Roger Light, Mosquitto's maintainer, says users are "strongly recommended to upgrade to 2.1.4."
Eclipse, the CNA, rates it 9.8 Critical. It affects Mosquitto 2.1.0 through 2.1.2, and only listeners set to protocol websockets on builds that use Mosquitto's built-in WebSocket code. The CVE record says the bug triggers before authentication, so allow_anonymous false does not stop it. Eclipse published the fix on November 17, 2026. If you can't upgrade today, Eclipse says to stop using WebSocket listeners or to build with libwebsockets.
No exploitation has been reported, and it is not on CISA's Known Exploited Vulnerabilities catalog. Public proof-of-concept code runs against Mosquitto built from source and shows the broker misreading the connection. It does not show code execution.
Is it reachable for you?
What it is. MQTT clients such as browsers and dashboards can talk to Mosquitto over WebSockets. Mosquitto 2.1 added its own WebSocket code. The CVE record says that code mishandles empty WebSocket data frames, which lets a client make the broker read memory it never received and then write past the end of a buffer. The CVE record says combining the two allows code execution as the broker's user.
Three conditions, all needed. The broker runs 2.1.0, 2.1.1 or 2.1.2. It was built with the built-in WebSocket implementation. It has a listener set to protocol websockets that an attacker can reach. No account is needed.
Checks, in three tiers. The first two decide exposure. The third decides priority. Run these only on systems your organization owns.
- Which brokers run Mosquitto 2.1.0 to 2.1.2? Check installed packages and container image tags, including Mosquitto bundled inside other products and appliances. Version 2.0.x is not listed for this flaw.
- Does any listener use WebSockets? Search mosquitto.conf and every included file for a
listenerblock withprotocol websockets. Eclipse says builds that use libwebsockets avoid the flaw, so ask your packager which WebSocket implementation your build uses if you didn't compile it yourself. - Who can reach that listener? Test from the internet and from user networks. A WebSocket listener reachable from the internet comes first, since no login is needed.
Compensating controls (test them, don't assume them)
Upgrading to 2.1.4 is the fix. Eclipse gives two stopgaps for brokers that can't be upgraded today.
- Stop using WebSocket listeners. Remove or comment out the
protocol websocketslistener and restart the broker, per Eclipse. Only if no clients depend on MQTT over WebSockets, since they will lose their connection. - Build with libwebsockets. Eclipse says compiling Mosquitto with libwebsockets support instead of the built-in implementation mitigates the flaw. Only if you build Mosquitto yourself.
What to look for in logs
Eclipse has published no indicators of compromise for CVE-2026-110486. The CVE record says an attacker can crash the broker with this flaw, even with allow_anonymous false set.
FAQ
Am I exposed to CVE-2026-110486?
You are if a Mosquitto 2.1.0 to 2.1.2 broker built with the built-in WebSocket implementation has a protocol websockets listener that an attacker can reach. No credentials are needed.
Is CVE-2026-110486 being exploited?
No exploitation has been reported, and it is not on CISA KEV. Public proof-of-concept code exists. It was tested on Mosquitto built from source and shows the broker misreading the connection, without code execution.
Which fixed version should I install?
Mosquitto 2.1.4. Eclipse's advisory lists 2.1.3 as fixed. Eclipse's release post says 2.1.3 introduced a regression that always rejects legacy sha512 passwords, fixed in 2.1.4, and Roger Light's notice recommends 2.1.4.
I run the Home Assistant Mosquitto app. Am I affected?
The app runs Mosquitto 2.1.2. Its version 7.1.2 (October 19) added a fix for WebSocket data frames with an empty payload in the built-in listener, and 7.1.3 stopped building libwebsockets. Neither changelog names CVE-2026-110486, and Home Assistant has not said whether that fix covers it. Check the app's changelog for a Mosquitto 2.1.4 update.
Did the same release fix anything else?
Yes. CVE-2026-126708 (High) affects 2.0.0 to 2.0.22 and 2.1.0 to 2.1.2. Eclipse says that with OpenSSL 4.0 and its FIPS provider, any password shorter than 8 characters can match another short password. It is fixed in 2.0.23 and 2.1.3.
- Vendor
- Eclipse Foundation (Eclipse Mosquitto)
- Product
- Eclipse Mosquitto MQTT broker, built with its built-in WebSocket support
- Affected versions
- 2.1.0 through 2.1.2 (Eclipse advisory GHSA-6j8m-r32v-4h38). Only listeners configured with protocol websockets on builds that use the built-in WebSocket implementation. Mosquitto 2.0.x is not listed
- Vulnerable component
- Built-in WebSocket implementation (lib/net_ws.c) and the MQTT packet reader, per the CVE record
- CVSS
- 9.8 Critical (Eclipse as CNA, CVSS 3.1). NVD has not added its own score
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (Eclipse)
- CWE
- CWE-787 Out-of-bounds Write (Eclipse)
- Exploitation
- Not observed
- CISA KEV added
- Patch
- Mosquitto 2.1.4. Eclipse's advisory lists 2.1.3 as the fixed version, but Eclipse's release post says 2.1.3 introduced a regression that rejects legacy sha512 passwords, fixed in 2.1.4, and Roger Light's oss-security notice says to upgrade to 2.1.4
Updates
Nov 19, 2026. First published. Eclipse fixed CVE-2026-110486 on November 17 and recommends Mosquitto 2.1.4. Public proof-of-concept code shows the bug without code execution. No exploitation reported; not on CISA KEV (catalog 2026.11.18).
Sources
- Eclipse Mosquitto advisory GHSA-6j8m-r32v-4h38 (Nov 17, 2026; affected 2.1.0 to 2.1.2, workarounds, credit orosec)
- Roger Light, oss-security notice for CVE-2026-110486 (Nov 17, 2026; recommends 2.1.4)
- Eclipse Mosquitto blog, Version 2.1.4, 2.0.23 released (Nov 17, 2026; 2.1.3 legacy sha512 regression)
- CVE record CVE-2026-110486 (CNA Eclipse, published Nov 18, 2026) and NIST NVD (Received, Eclipse's 9.8 only, checked Nov 19)
- Eclipse Mosquitto advisory GHSA-878w-672v-qwmf, CVE-2026-126708 and oss-security notice
- Public proof of concept, googlesky/CVE-2026-110486 (lab build from source; parser desync only; read only, not run)
- Home Assistant Mosquitto app changelog and pull request 4868 (Oct 19, 2026)
- CISA Known Exploited Vulnerabilities catalog (not listed; checked catalog version 2026.11.18)
We publish an advisory when a vulnerability is Critical or on CISA KEV, has one identifiable component to check, and has a public proof of concept or reported exploitation. Advisories are updated as exploitation status changes.