Low 2.0Published Sep 18, 2026

CVE-2026-61633NanoMQ: Infinite Loop in UNSUBSCRIBE Decoder Leading to Remote DoS

Updated under an hour ago (2026-10-19 10:10 UTC)

Does this affect you?

It affects nanomq. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for nanomq

Exploited in the last 30 days

NanoMQ is an MQTT broker. Prior to 0.24.14, the NanoMQ client function nni_mqtt_msg_decode_unsubscribe() in nng/src/supplemental/mqtt/mqtt_codec.c does not handle a failed read_uint16() while counting topics in a malformed UNSUBSCRIBE packet. A zero-length topic followed by trailing data can leave buf.curpos unchanged while topic_count continues to increase, allowing a malicious MQTT broker to hang a connecting MQTT 3.1.1 client, consume CPU and memory, and repeatedly deny service when automatic reconnection is enabled. The broker-side nmq_unsubinfo_decode path is not affected. This issue is fixed in version 0.24.14.

CVSS: 2.0 LOW (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:N/I:N/A:L
Weakness (CWE): CWE-835
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: GitHub_M
NVD analysis: Deferred
Record last updated: Sep 18, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

nanomq nanomq nanomq:nanomq (from the name)	before 0.24.14	CNA record

References

https://github.com/nanomq/nanomq/security/advisories/GHSA-m7mp-rr3v-hmhrx-refsource-confirm
https://github.com/nanomq/NanoNNG/pull/1518x-refsource-misc
https://github.com/nanomq/NanoNNG/commit/fa8d859bb39841e46cfc6cce280d242bd782ad3dx-refsource-misc
https://github.com/nanomq/nanomq/releases/tag/0.24.14x-refsource-misc

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.