CVE
Eclipse Mosquitto remote code execution in WebSocket frame handling
Only affects Mosquitto 2.1.0 through 2.1.2 with a websockets listener using the built-in implementation, not libwebsockets. No vendor severity rating or fixed version is listed.
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Not reported
Do first: Workaround: The checked facts name no vendor workaround. The condition is a websockets listener on the built-in implementation, so limiting that listener is the feature to restrict while no fix is available.
Summary
Eclipse Mosquitto is affected. A remote client can, without logging in, send empty WebSocket data frames to a listener configured for websockets, causing the broker to read uninitialised heap memory and write past the end of an allocation. The flaw can leak heap and library pointers and crash the broker even when anonymous access is disabled. Combined, the leak and the write can allow remote code execution as the broker's user.
Original description
In Eclipse Mosquitto versions 2.1 through 2.1.2, a listener configured with protocol websockets mishandles empty WebSocket data frames. net__read_ws() in lib/net_ws.c returns the number of framing bytes consumed (the 4 masking-key bytes) for a data frame with a zero-length payload, without writing any bytes to the caller’s buffer. The MQTT packet reader in packet__read_single() (lib/packet_mosq.c) trusts that return value as a payload byte count. A remote client can therefore advance the read position over an uninitialised heap allocation, causing the broker to process and forward uninitialised heap memory (information disclosure, including heap and libc pointers), and can underflow the unsigned to_process counter so that subsequent attacker-controlled frame data is written past the end of the allocation (heap out-of-bounds write). The out-of-bounds write is reachable from the CONNECT packet before any authentication check, so an unauthenticated client can corrupt the heap and crash the broker even when allow_anonymous false is set. Combining the disclosure and the write allows remote code execution as the broker’s user by any client able to establish a session.
Who should check
Teams running Eclipse Mosquitto 2.1.0 to 2.1.2 with a websockets listener using the built-in implementation
“Eclipse Mosquitto versions 2.1.0 to 2.1.2 contains a vulnerability”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 9.8
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 37 if advisories confirm default setups are exposed
What to do
Workaround: The checked facts name no vendor workaround. The condition is a websockets listener on the built-in implementation, so limiting that listener is the feature to restrict while no fix is available.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-110486 (Remote heap out-of-bounds read/write in Eclipse Mosquitto), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-110486 (entry last updated 2026-11-18):
Affected:
- Eclipse Foundation Eclipse Mosquitto: from 2.1, through 2.1.2
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Listener configured with websockets protocol using Mosquitto's built-in websockets implementation (not libwebsockets) (source: https://github.com/eclipse-mosquitto/mosquitto/security/advisories/GHSA-6j8m-r32v-4h38)
- Affected Mosquitto versions 2.1.0 through 2.1.2 (source: https://github.com/eclipse-mosquitto/mosquitto/security/advisories/GHSA-6j8m-r32v-4h38)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-110486 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110486 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/521
- https://github.com/eclipse-mosquitto/mosquitto/security/advisories/GHSA-6j8m-r32v-4h38
- https://gitlab.eclipse.org/security/cve-assignment/-/work_items/399
- http://www.openwall.com/lists/oss-security/2026/11/17/14
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-110486
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110486"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- Record last updated
Affected versions
- Eclipse Foundation Eclipse Mosquitto
From 2.1 · through 2.1.2
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 3Establishes: Affected and fixed versions. | |
| Advisory | GitHub · eclipse-mosquitto/mosquitto · Advisory GHSA-6j8m-r32v-4h38 |
| Link | gitlab.eclipse.org · security/vulnerability-reports/-/work_items/521 |
| Link | gitlab.eclipse.org · security/cve-assignment/-/work_items/399 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-110486 |
| Record | NVD · CVE-2026-110486 |
| Write-ups 1Establishes: Technical detail and context. | |
| Link | openwall.com · lists/oss-security/2026/11/17/14 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-110486
Is CVE-2026-110486 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The broker has an out-of-bounds write that can corrupt heap memory. The issue allows unauthenticated remote code execution as the broker process when a built-in websockets listener is used.Source: github.com
Which versions are affected by CVE-2026-110486?
Eclipse Mosquitto: from 2.1 through 2.1.2.Source: cve.now feed data
Am I affected, and how do I check?
Mosquitto versions 2.1.0 through 2.1.2 are affected, and only when a listener is configured with the websockets protocol using Mosquitto's built-in websockets implementation rather than libwebsockets. Check the broker version and the listener configuration for a websockets protocol setting.Source: github.com
How do I fix CVE-2026-110486?
The checked facts name no fixed version and no patch identifiers, so no upgrade target can be given from them. Check the Eclipse Mosquitto project's advisory for a fix before relying on any version.Source: github.com
What if there's no patch?
The checked facts name no vendor workaround. The condition is a websockets listener on the built-in implementation, so limiting that listener is the feature to restrict while no fix is available.Source: github.com