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.
CVE-2026-61633
LOWPre-NVD 2.02.0Elevated
EchelonGraph scoreLOW confidence
This low-severity CVE scores 2.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
2.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.0Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 2.0
- EG Score
- 2.0(low)
- EG Risk
- 25(Track)EG Risk 25/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity20% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 17%
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
References (5)
- security-advisories@githubhttps://github.com/nanomq/NanoNNG/commit/fa8d859bb39841e46cfc6cce280d242bd782ad3d
- security-advisories@githubhttps://github.com/nanomq/NanoNNG/pull/1518
- security-advisories@githubhttps://github.com/nanomq/nanomq/releases/tag/0.24.14
- security-advisories@githubhttps://github.com/nanomq/nanomq/security/advisories/GHSA-m7mp-rr3v-hmhr
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/nanomq/nanomq/security/advisories/GHSA-m7mp-rr3v-hmhr
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 18:27 UTCEG score recompute
- 2026-09-18 17:34 UTCEG score recompute
- 2026-09-18 17:26 UTCEG score recompute
- 2026-09-18 16:29 UTCEG score recompute
- 2026-09-18 16:29 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-835
Frequently asked(5)
What is CVE-2026-61633?
CVE-2026-61633 is a low vulnerability published on September 18, 2026. NanoMQ is an MQTT broker. Prior to 0.24.14, the NanoMQ client function nnimqttmsgdecodeunsubscribe() in nng/src/supplemental/mqtt/mqttcodec.c does not handle a failed readuint16() while counting topics in a malformed UNSUBSCRIBE packet. A zero-length topic followed by trailing data can leave…
When was CVE-2026-61633 disclosed?
CVE-2026-61633 was first published in the National Vulnerability Database on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-61633 actively exploited?
CVE-2026-61633 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 82.8% of all scored CVEs.
What is the CVSS score of CVE-2026-61633?
CVE-2026-61633 has a CVSS v3 base score of 2.0 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-61633?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-61633, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-61633
Is Your Infrastructure Affected by CVE-2026-61633?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.