Eclipse Foundation · Eclipse Mosquitto · CWE-787 · CWE-908 · CWE-191 · published 2026-11-18
CVE-2026-110486Remote heap out-of-bounds read/write in Eclipse Mosquitto
This month Public proof-of-concept exists (SSVC exploitation: poc).
CVE-2026-110486 has a public proof-of-concept exploit, but no confirmed exploitation in the wild. EPSS estimates a 1.0% chance of exploitation in the next 30 days, higher than 64% of all CVEs. This Eclipse Mosquitto vulnerability: CVSS 9.8 (v3.1), attacks can be automated, a successful attack gives total control of the component. Patch in your normal monthly cycle.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
No fixed version is recorded here yet. Check the vendor advisory linked from the CVE record below.
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 1.0% (65th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 9.8 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | CNA / CISA ADP |
| SSVC exploitation | poc | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | total | CISA Vulnrichment |
Weakness: CWE-787: Out-of-bounds Write · CWE-908: Use of Uninitialized Resource · CWE-191: Integer Underflow (Wrap or Wraparound)
Affected versions (from the CVE record)#
- Eclipse Foundation Eclipse Mosquitto
2.1through2.1.2(affected)
Description (from the CVE record)#
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.
Quoted from the CVE Program record.