CVE-2025-70290

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-26. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 4 sources updated this week
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.7%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

An issue was discovered in Denx U-Boot before 2026.04. An integer overflow vulnerability in the ZFS filesystem support can be triggered by malformed on-disk metadata. The issue may result in incorrect memory allocation followed by out-of-bounds memory access, potentially leading to a crash or arbitrary code execution during the boot process.

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.7% × 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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
51st
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.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-22). 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).

A fix is available. 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

August 26, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Oct 15, 2026
Patch available.
Web pageMentions a patch (unverified)

U-Boot integer overflows in filesystem parsing · GitHub

https://gist.github.com/c0zy1/4d9648d10a5ff07bda2771ea1298e469
Web page

U-Boot – deinde.dev

http://u-boot.com

Vendor Advisories for CVE-2025-70290(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntuu-boot-tools (2025.10-0ubuntu0.24.04.3) @ noble2026-10-23ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
u-boot2023.01+dfsg-2 ... 2025.01-3.2 (24 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
u-boot2025.01-3, 2025.01-3+deb13u1, 2025.01-3.1, 2025.01-3.2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
u-boot2025.01-3, 2025.01-3.1, 2025.01-3.2
  • every version on: no fix on record
—

Weakness Classification(2)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 24× in last 7d / 144× 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 353 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 253 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2025-70290?
CVE-2025-70290 is a critical-severity vulnerability; its CVE record was published on August 26, 2026. An issue was discovered in Denx U-Boot before 2026.04. An integer overflow vulnerability in the ZFS filesystem support can be triggered by malformed on-disk metadata. The issue may result in incorrect memory allocation followed by out-of-bounds memory access, potentially leading to a crash or…
When was the CVE record for CVE-2025-70290 published?
The CVE record for CVE-2025-70290 was published on August 26, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2025-70290 actively exploited?
CVE-2025-70290 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-70290?
CVE-2025-70290 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2025-70290?
A fix for CVE-2025-70290 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-70290 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-70290

Explore →

Is Your Infrastructure Affected by CVE-2025-70290?

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