CVE-2026-36590

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-07-16. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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

An issue in EMQ NanoMQ v.0.24.9 allows a remote attacker to cause a denial of service via the nni_qos_db_set function in broker_tcp.c component

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
32.7%
KEV
Not listed

Published

July 15, 2026

Last Modified

July 16, 2026

Advisory Details (2)

Auto-updated Jul 16, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

NanoMQ-Memory-Leak-Research/README.md at main · MoXie25/NanoMQ-Memory-Leak-Research · GitHub

https://github.com/MoXie25/NanoMQ-Memory-Leak-Research/blob/main/README.md
generic🟡 PoC Available

GitHub - MoXie25/NanoMQ-Memory-Leak-Research: Public advisory and technical analysis for CVE-2026-36590, a NanoMQ v0.24.9 denial-of-service vulnerability. · GitHub

https://github.com/MoXie25/NanoMQ-Memory-Leak-Research.git

Vendor Advisories for CVE-2026-36590(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 14× 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-07-23 03:10 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-17 06:47 UTCEG score recompute▲ 7.50
  9. 2026-07-17 06:47 UTCGHSA enrichment
  10. 2026-07-16 19:14 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-15 22:24 UTCNVD update
  13. 2026-07-15 22:09 UTCEG score recompute
  14. 2026-07-15 22:08 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-36590?
CVE-2026-36590 is a high vulnerability published on July 15, 2026. An issue in EMQ NanoMQ v.0.24.9 allows a remote attacker to cause a denial of service via the nniqosdbset function in brokertcp.c component
When was CVE-2026-36590 disclosed?
CVE-2026-36590 was first published in the National Vulnerability Database on July 15, 2026, with the most recent update on July 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-36590 actively exploited?
CVE-2026-36590 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 32.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-36590?
CVE-2026-36590 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-36590?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-36590, 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-36590

Explore →

Is Your Infrastructure Affected by CVE-2026-36590?

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

Start Free Scan →Browse All CVEs