CVE-2026-61633

Published: Set 18, 2026 Last Modified: Set 18, 2026
ExploitDB:
Other exploit source:
Google Dorks:
LOW 2,0
Attack Vector: network
Attack Complexity: high
Privileges Required: high
User Interaction: required
Scope: unchanged
Confidentiality: none
Integrity: none
Availability: low

Description

AI Translation Available

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.

835

Loop with Unreachable Exit Condition ('Infinite Loop')

Incomplete
Common Consequences
Security Scopes Affected:
Availability
Potential Impacts:
Dos: Resource Consumption (Cpu) Dos: Resource Consumption (Memory) Dos: Amplification
Applicable Platforms
All platforms may be affected
View CWE Details
https://github.com/nanomq/nanomq/security/advisories/GHSA-m7mp-rr3v-hmhr
https://github.com/nanomq/nanomq/releases/tag/0.24.14
https://github.com/nanomq/nanomq/security/advisories/GHSA-m7mp-rr3v-hmhr
https://github.com/nanomq/NanoNNG/commit/fa8d859bb39841e46cfc6cce280d242bd782ad…
https://github.com/nanomq/NanoNNG/pull/1518