CVE-2026-32134

MEDIUMNVD 5.95.9
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated
5.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.9Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. In versions 0.24.10 and below, when NanoMQ handles high-concurrency reconnect traffic using a reconnect-collision payload, the broker can crash due to a NULL pointer dereference during MQTT session resumption for clean_start=0 clients. The transport's p_peer callback (tcptran_pipe_peer()) iterates cpipe->subinfol while copying session metadata from the cached old pipe to the new reconnecting pipe, without checking whether the pointer is NULL. Under a reconnect race, cpipe->subinfol can be freed and set to NULL before session restore invokes this function, resulting in a remote unauthenticated Denial-of-Service (process crash) condition. This issue has been fixed in version 0.24.11.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
43
EG Risk 43/100

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 (value × EchelonGraph’s weight)
Severity59% × 45%
The EG Score, 5.9 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The CVE record names the fixed release. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 19, 2026

Last Modified

July 24, 2026

Advisory Details (4)

Auto-updated May 20, 2026
Fix named in the CVE record. Sources: github.
GitHub advisoryMentions a patch (unverified)

NanoMQ v0.24.10-14 Session Restore Feature: NULL Pointer Dereference Crash in `tcptran_pipe_peer` · Advisory · nanomq/nanomq · GitHub

https://github.com/nanomq/nanomq/security/advisories/GHSA-q36f-83mh-pcv2
Web page

NanoMQ v0.24.10-14 Session Restore Feature: NULL Pointer Dereference Crash in `tcptran_pipe_peer` · Issue #2241 · nanomq/nanomq · GitHub

https://github.com/nanomq/nanomq/issues/2241
Web page

Release NanoMQ 0.24.11 · nanomq/nanomq · GitHub

https://github.com/nanomq/nanomq/releases/tag/0.24.11
Web page

* MDF [trasnport/mqtt] add more null checker base on review · nanomq/NanoNNG@522ec62 · GitHub

https://github.com/nanomq/NanoNNG/commit/522ec62e29e60d1122f2aedaa6e702dcf089f7bb

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 27× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 92 of 192 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 8 repeat rows among the latest 100 are merged into the row they repeat. The 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  3. 2026-10-12 16:14 UTCEG score recompute
  4. 2026-10-11 19:56 UTCEG score recompute
  5. 2026-10-11 17:10 UTCEG score recompute
  6. 2026-10-11 14:38 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  12. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  16. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  17. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  18. 2026-09-30 03:39 UTCOSV refresh
  19. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  20. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  21. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  23. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  25. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
Show 67 more
  1. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  4. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-09-11 05:53 UTCOSV refresh
  7. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  14. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  18. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  20. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-08-23 17:00 UTCEG score recompute
  22. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  23. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-08-21 23:37 UTCEG score recompute
  25. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  26. 2026-08-20 19:01 UTCEG score recompute
  27. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  28. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  29. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  30. 2026-08-17 09:59 UTCEG score recompute
  31. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  32. 2026-08-16 03:34 UTCEG score recompute
  33. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  34. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  35. 2026-08-14 02:06 UTCEG score recompute
  36. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  37. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  38. 2026-08-12 11:59 UTCEG score recompute
  39. 2026-08-11 08:07 UTCEG score recompute
  40. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  41. 2026-08-10 06:21 UTCEG score recompute
  42. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  43. 2026-08-09 04:37 UTCEG score recompute
  44. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  45. 2026-08-08 02:53 UTCEG score recompute
  46. 2026-08-07 01:09 UTCEG score recompute
  47. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  48. 2026-08-05 21:20 UTCEG score recompute
  49. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  50. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  51. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  52. 2026-08-03 21:22 UTCEG score recompute
  53. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  54. 2026-08-02 19:38 UTCEG score recompute
  55. 2026-08-02 02:27 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  56. 2026-08-01 17:53 UTCEG score recompute
  57. 2026-08-01 04:16 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  58. 2026-07-30 16:28 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  59. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  60. 2026-07-28 15:36 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  61. 2026-07-26 14:54 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  62. 2026-07-26 08:19 UTCEG score recompute
  63. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  64. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  65. 2026-07-23 03:08 UTCEG score recompute
  66. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  67. 2026-07-21 15:24 UTCEPSS rescoreEPSS 0.4% · 32nd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-32134?
CVE-2026-32134 is a medium-severity vulnerability; its CVE record was published on May 19, 2026. NanoMQ MQTT Broker (NanoMQ) is an all-around Edge Messaging Platform. In versions 0.24.10 and below, when NanoMQ handles high-concurrency reconnect traffic using a reconnect-collision payload, the broker can crash due to a NULL pointer dereference during MQTT session resumption for cleanstart=0…
When was the CVE record for CVE-2026-32134 published?
The CVE record for CVE-2026-32134 was published on May 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-32134 actively exploited?
CVE-2026-32134 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32134?
CVE-2026-32134 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-32134?
The CVE record for CVE-2026-32134 names the fix: "This issue has been fixed in version 0.24.11."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-32134

Explore →

Is Your Infrastructure Affected by CVE-2026-32134?

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

Book a Demo →Browse All CVEs