CVE-2026-47276

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. 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: epss, secondary
Elevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In nanomq versions 0.24.11 and earlier, a NULL pointer dereference in properties_parse() allows an authenticated attacker to crash the NanoMQ broker by sending a POST request to /api/v4/mqtt/publish with user_properties as a JSON array instead of a JSON object. The crash occurs because strlen() is called on a NULL item->string pointer when iterating over array elements. An authenticated attacker can exploit this to crash the NanoMQ broker process. This is patched in version 0.24.14.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
45(Track)
EG Risk 45/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 computed
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

July 20, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jul 20, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

NULL Pointer Dereference in REST API properties_parse via Malformed user_properties · Advisory · nanomq/nanomq · GitHub

https://github.com/nanomq/nanomq/security/advisories/GHSA-qq2v-xvxg-3hvf

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 51× 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.

  1. 2026-08-30 02:35 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 22:13 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-26 22:27 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 22:40 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 22:01 UTCEG score recompute
  11. 2026-08-23 22:15 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 22:16 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 22:29 UTCEG score recompute
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 22:56 UTCEG score recompute
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 23:09 UTCEG score recompute
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 23:23 UTCEG score recompute
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 23:36 UTCEG score recompute
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 45 more
  1. 2026-08-15 23:50 UTCEG score recompute
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 00:17 UTCEG score recompute
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 00:30 UTCEG score recompute
  6. 2026-08-12 13:51 UTCEPSS rescore
  7. 2026-08-12 00:44 UTCEG score recompute
  8. 2026-08-11 00:58 UTCEG score recompute
  9. 2026-08-11 00:00 UTCEPSS rescore
  10. 2026-08-10 01:11 UTCEG score recompute
  11. 2026-08-09 13:46 UTCEPSS rescore
  12. 2026-08-09 01:25 UTCEG score recompute
  13. 2026-08-08 16:37 UTCEPSS rescore
  14. 2026-08-08 01:38 UTCEG score recompute
  15. 2026-08-07 01:52 UTCEG score recompute
  16. 2026-08-06 13:47 UTCEPSS rescore
  17. 2026-08-06 02:06 UTCEG score recompute
  18. 2026-08-05 19:17 UTCEPSS rescore
  19. 2026-08-05 02:20 UTCEG score recompute
  20. 2026-08-04 15:10 UTCEPSS rescore
  21. 2026-08-04 10:39 UTCEPSS rescore
  22. 2026-08-04 02:33 UTCEG score recompute
  23. 2026-08-03 10:36 UTCEPSS rescore
  24. 2026-08-02 03:00 UTCEG score recompute
  25. 2026-08-02 02:27 UTCEPSS rescore
  26. 2026-08-01 04:16 UTCEPSS rescore
  27. 2026-07-31 03:26 UTCEG score recompute
  28. 2026-07-30 16:28 UTCEPSS rescore
  29. 2026-07-30 03:40 UTCEG score recompute
  30. 2026-07-30 01:30 UTCEPSS rescore
  31. 2026-07-29 03:52 UTCEG score recompute
  32. 2026-07-28 15:37 UTCEPSS rescore
  33. 2026-07-28 04:04 UTCEG score recompute
  34. 2026-07-27 04:18 UTCEG score recompute
  35. 2026-07-26 14:54 UTCEPSS rescore
  36. 2026-07-26 04:29 UTCEG score recompute
  37. 2026-07-25 14:18 UTCEPSS rescore
  38. 2026-07-24 14:18 UTCEPSS rescore
  39. 2026-07-23 14:18 UTCEPSS rescore
  40. 2026-07-23 03:17 UTCEG score recompute
  41. 2026-07-22 14:08 UTCEPSS rescore
  42. 2026-07-21 15:24 UTCEPSS rescore
  43. 2026-07-20 18:41 UTCEG score recompute
  44. 2026-07-20 17:11 UTCEG score recompute
  45. 2026-07-20 17:09 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-47276?
CVE-2026-47276 is a medium vulnerability published on July 20, 2026. In nanomq versions 0.24.11 and earlier, a NULL pointer dereference in propertiesparse() allows an authenticated attacker to crash the NanoMQ broker by sending a POST request to /api/v4/mqtt/publish with userproperties as a JSON array instead of a JSON object. The crash occurs because strlen() is…
When was CVE-2026-47276 disclosed?
CVE-2026-47276 was first published in the National Vulnerability Database on July 20, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47276 actively exploited?
CVE-2026-47276 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 66.0% of all scored CVEs.
What is the CVSS score of CVE-2026-47276?
CVE-2026-47276 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-47276?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47276, 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-47276

Explore →

Is Your Infrastructure Affected by CVE-2026-47276?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs