CVE-2025-26237

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

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

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.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.1Exploit: None knownExposed services: Not assessed

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

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-18). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

August 24, 2026

Last Modified

September 29, 2026

Advisory Details (1)

Auto-updated Aug 28, 2026
No fix on record yet.
Web page

iot/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.md

Vendor 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 10× in last 7d / 86× 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 98 of 181 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 83 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-26237?
CVE-2025-26237 is a high-severity vulnerability; its CVE record was published on August 24, 2026. D-Link DI-7001 MINI5G 19.10.31A1 contains a code execution vulnerability in the flag parameter of mspinfo, which can be exploited to run arbitrary commands.
When was the CVE record for CVE-2025-26237 published?
The CVE record for CVE-2025-26237 was published on August 24, 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 September 29, 2026; the record at its source may have been updated since.
Is CVE-2025-26237 actively exploited?
CVE-2025-26237 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-26237?
CVE-2025-26237 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-26237?
No fix for CVE-2025-26237 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2025-26237 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-26237

Explore →

Is Your Infrastructure Affected by CVE-2025-26237?

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