CVE-2026-35217: NanoMQ Incorrectly Accepts a Malformed SUBSCRIBE and Can Be Driven into an ASAN-Detectable Out-of-Bounds Read
NanoMQ contains a protocol-semantics flaw in its MQTT v5 SUBSCRIBE handling: if a subscription entry is missing the final 1-byte Subscription Options field, the broker may still accept the malformed packet and install the subscription into internal broker state. Under a specific packet-length construction, the same parser flaw also causes a 1-byte out-of-bounds read that crosses the real heap allocation boundary and is detected by ASAN as a heap-buffer-overflow.
If the consumed byte happens to look acceptable, NanoMQ may continue and append the malformed subscription entry into its internal subinfol state. In that case, a SUBSCRIBE packet that should be rejected by MQTT rules is instead treated as a successful subscription. Whether ASAN reports the bug does not depend on MQTT's logical remain boundary; it depends on whether the read crosses the real heap allocation boundary of the underlying message buffer. In other words, these are not two unrelated issues. They are two manifestations of the same parsing defect: by default, it appears as a semantic vulnerability, and under suitable input conditions, it also becomes a verifiable out-of-bounds read vulnerability.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-35217?
CVE-2026-35217 has a medium severity rating of 6.5.
What are the implications of CVE-2026-35217?
CVE-2026-35217 allows NanoMQ to accept malformed SUBSCRIBE packets, potentially leading to out-of-bounds reads.
How do I fix CVE-2026-35217?
To fix CVE-2026-35217, update NanoMQ to the latest version where this vulnerability has been addressed.
Which software is affected by CVE-2026-35217?
CVE-2026-35217 affects the NanoMQ software.
What is the main issue described in CVE-2026-35217?
The main issue in CVE-2026-35217 is that NanoMQ incorrectly handles malformed SUBSCRIBE packets, potentially compromising its internal state.