NanoMQ is an MQTT broker. Prior to 0.24.14, NanoMQ's MQTT v5 property decoder in nng/src/supplemental/mqtt/mqtt_codec.c uses property_append() to walk the entire linked list for each property added by decode_buf_properties(). A remote unauthenticated client can supply a PUBLISH or SUBSCRIBE packet containing many User Properties, causing O(N²) linked-list insertion and CPU work that makes the broker unresponsive; repeated packets can sustain the denial of service. This issue is fixed in version 0.24.14.
CVE-2026-44639
LOWPre-NVD 3.73.7Elevated
EchelonGraph scoreLOW confidence
This low-severity CVE scores 3.7 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
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 3.7Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.7
- EG Score
- 3.7(low)
- EG Risk
- 33(Track)EG Risk 33/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 computedSeverity37% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
References (5)
- security-advisories@githubhttps://github.com/nanomq/NanoNNG/commit/91bd4c7f45f945a3f5f0e37c459157dc7c277a07
- security-advisories@githubhttps://github.com/nanomq/NanoNNG/pull/1508
- security-advisories@githubhttps://github.com/nanomq/nanomq/releases/tag/0.24.14
- security-advisories@githubhttps://github.com/nanomq/nanomq/security/advisories/GHSA-6mwg-445v-2qrv
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/nanomq/nanomq/security/advisories/GHSA-6mwg-445v-2qrv
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× 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:26 UTCEG score recompute
- 2026-09-18 16:29 UTCEG score recompute
- 2026-09-18 16:29 UTCMITRE cvelistV5first tracked
Frequently asked(4)
What is CVE-2026-44639?
CVE-2026-44639 is a low vulnerability published on September 18, 2026. NanoMQ is an MQTT broker. Prior to 0.24.14, NanoMQ's MQTT v5 property decoder in nng/src/supplemental/mqtt/mqttcodec.c uses propertyappend() to walk the entire linked list for each property added by decodebufproperties(). A remote unauthenticated client can supply a PUBLISH or SUBSCRIBE packet…
When was CVE-2026-44639 disclosed?
CVE-2026-44639 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.
What is the CVSS score of CVE-2026-44639?
CVE-2026-44639 has a CVSS v3 base score of 3.7 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-44639?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44639, 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-44639
Is Your Infrastructure Affected by CVE-2026-44639?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.