CVE-2026-1951

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-24. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-25403 (ENISA EUVD) · GHSA-cc2v-9v42-3c8q (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 9.8Exploit: None knownExposed services: Not assessed

Upgrade firmware to v1.12 or later (from the CVE record's solution, Delta Electronics, Inc.) — apply it.

Delta Electronics AS320T has no checking of the length of the buffer with the directory name

vulnerability.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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: Upgrade firmware to v1.12 or later (from the CVE record's solution, Delta Electronics, Inc.). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
49th
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

Upgrade firmware to v1.12 or later (from the CVE record's solution, Delta Electronics, Inc.). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

April 24, 2026

Last Modified

October 26, 2026

Advisory Details (1)

Auto-updated Oct 26, 2026
Fix named in the CVE record's solution (Delta Electronics, Inc.).

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 69× 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 100 of 355 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. None are among the latest 100 rows. The 255 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-1951?
CVE-2026-1951 is a critical-severity vulnerability; its CVE record was published on April 24, 2026. Delta Electronics AS320T has no checking of the length of the buffer with the directory name vulnerability.
When was CVE-2026-1951 made public?
CVE-2026-1951 was made public on April 24, 2026: that is the date its CVE record's CNA, Delta Electronics, Inc., gives for when the vulnerability was made public. The CVE record itself was published on April 24, 2026. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-1951 actively exploited?
CVE-2026-1951 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-1951?
CVE-2026-1951 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-1951?
The CVE record's solution for CVE-2026-1951, written by its CNA Delta Electronics, Inc., names the fix: "Upgrade firmware to v1.12 or later".

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-1951?

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