CVE-2026-110486

9.8Critical

Published 18 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

9.8CVSS

Critical

0CVSS v3.110

Attack vector
Network
Complexity
Low
Privileges
None
User action
None
Impact
Full C/I/A compromise
Weakness
CWE-191, CWE-787, CWE-908

What an attacker gets

Unauthenticated remote attackers can execute arbitrary code as the broker user or crash the service. This is achieved by sending crafted WebSocket frames to trigger heap corruption and information disclosure.

Root cause

The WebSocket listener incorrectly calculates payload lengths for zero-length frames, leading to an integer underflow and out-of-bounds heap access.

Affected versions

Eclipse Mosquitto 2.1 through 2.1.2

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Fix & remediation

Upgrade to Mosquitto 2.1.3 or later. If you cannot patch immediately, disable all listeners configured with 'protocol websockets' in your mosquitto.conf.

remediation — bash
$ sudo apt-get update && sudo apt-get install --only-upgrade mosquitto

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-110486