Skip to content- Sources: primary, discussion
- Summary: A researcher shows that a Mosquitto bug disclosed publicly in August 2026 and judged harmless in its GitHub issue lets an empty WebSocket frame return more bytes than requested, underflowing the packet length counter and writing past the payload buffer before authentication. The write-up builds a reliable exploit against the Home Assistant Mosquitto add-on. Affected are upstream 2.1.0 onward built with the built-in WebSocket listener exposed on the network, Eclipse expects fixed releases before 2026-11-18, and the Home Assistant add-on is fixed in 7.1.2.
- Why it matters: Anyone exposing Mosquitto's built-in MQTT-over-WebSocket listener should firewall or disable it until Eclipse ships a fix.
- Background: MQTT is a publish and subscribe protocol for IoT and machine-to-machine messaging, and Mosquitto is one of its most widely used open source brokers. Brokers can speak MQTT over raw TCP or wrapped in WebSocket frames for browser clients, so the broker must strip frame headers and reassemble MQTT packets across reads. The researcher found the flaw through a gap in Mosquitto's OSS-Fuzz harness, and says two frontier models pointed at the file flagged the length bug but missed its memory safety impact.
- Follow-up: Eclipse fixed Mosquitto releases expected before 2026-11-18, and the author's second post on the container escape.