D-Link DI-7001 MINI_5G 19.10.31A1 contains a code execution vulnerability in the flag parameter of msp_info, which can be exploited to run arbitrary commands.
CVE-2025-26237
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-24. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 37(Track)EG Risk 37/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 computedSeverity81% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 12%
- KEV
- Not listed
Published
August 24, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Aug 28, 2026iot/CVE/dlink/DI_7001_MINI_5G.md/DI_7001_MINI_5G.md at main · REYu6/iot · GitHub
https://github.com/REYu6/iot/blob/main/CVE/dlink/DI_7001_MINI_5G.md/DI_7001_MINI_5G.mdVendor Advisories for CVE-2025-26237(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 17× in last 7d / 17× 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-08-30 01:21 UTCEPSS rescore
- 2026-08-29 23:10 UTCGHSA enrichment
- 2026-08-29 10:26 UTCGHSA enrichment
- 2026-08-28 21:43 UTCEG score recompute
- 2026-08-28 21:42 UTCGHSA enrichment
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-28 20:45 UTCGHSA enrichment
- 2026-08-28 19:42 UTCEG score recompute▲ 8.10
- 2026-08-28 19:42 UTCGHSA enrichment
- 2026-08-28 19:36 UTCMITRE cvelistV5CVSS v3 → 8.1 · severity → HIGH
- 2026-08-28 00:45 UTCEG score recompute
- 2026-08-28 00:45 UTCGHSA enrichment
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-25 13:47 UTCEPSS rescore
- 2026-08-24 19:24 UTCNVD update
- 2026-08-24 18:51 UTCEG score recompute
- 2026-08-24 18:51 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-77
- CVE-2015-7541EG 10.0CRITICAL
- CVE-2015-1815EG 10.0EPSS p97HIGH
- CVE-2014-1905EG 10.0EPSS p95HIGH
- CVE-2013-2810EG 10.0EPSS p93HIGH
- CVE-2014-5470EG 9.8EPSS p95CRITICAL
- CVE-2013-2513EG 9.8CRITICAL
- CVE-2015-20108EG 9.8CRITICAL
- CVE-2015-10096NVD 5.0EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS p94CRITICAL
- CVE-2014-4982EG 9.8EPSS p91CRITICAL
Frequently asked(5)
What is CVE-2025-26237?
When was CVE-2025-26237 disclosed?
Is CVE-2025-26237 actively exploited?
What is the CVSS score of CVE-2025-26237?
How do I remediate CVE-2025-26237?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2025-26237
Is Your Infrastructure Affected by CVE-2025-26237?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.