Eclipse Foundation
Remote heap out-of-bounds read/write in Eclipse Mosquitto
Not on CISA's list of exploited flaws, and not in the news we track.
CVE-2026-110486Critical9.8
Severity
9.8of 10, critical
Black Shard's team can check your exposure to CVE-2026-110486 and take the fix off your plate.
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.
Updated 19 Nov 2026, 13:04 UTC, 32 of 36 sources answering.
Black Shard's team can check your exposure, take a fix off your plate or step in on a live incident.