CVE-2026-15390

CRITICALPre-NVD 9.09.0
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (9th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-88699 (ENISA EUVD) · GHSA-vm4x-pmjm-j3wm (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
EchelonGraph verdictPlan a fixRemediate 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: 9.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Das U-Boot with CONFIG_IP_DEFRAG=y parameter fails to clear IP reassembly state after delivering a complete datagram. An attacker who can deliver fragmented IP traffic can execute arbitrary code by sending duplicated last-fragment IP packets.

This issue was fixed in commit b1aec609bb5e0d08c25c888c91935287ab4ee5fa in version 2026.07.

CVSS
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
41
EG Risk 41/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)
Severity90% × 45%
Impact severity (EG Severity): CVSS 9.0 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
9th
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.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is its impact severity (EG Severity), not escalated.

EG Severity
9.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). 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, and whom BOD 26-04 binds: 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).

A fix is available. Apply it within your standard update timelines.

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.

The score's inputs: 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

September 29, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 29, 2026
Patch available.
Web page

net: clear IP defragmentation state after returning a complete packet (b1aec609) · Commits · u-boot / U-Boot · GitLab

https://source.denx.de/u-boot/u-boot/-/commit/b1aec609bb5e0d08c25c888c91935287ab4ee5fa
Web page

Vulnerability in Das U-Boot software | CERT Polska

https://cert.pl/en/posts/2026/09/CVE-2026-15390

Vendor Advisories for CVE-2026-15390(2)

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 (2016.01+dfsg1-2ubuntu5+esm1) @ xenial2026-11-20ubuntu

These rows come from Ubuntu. 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.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 20× in last 7d / 88× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 328 rows 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 228 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-15390?
CVE-2026-15390 is a critical-severity vulnerability; its CVE record was published on September 29, 2026. Das U-Boot with CONFIG_IP_DEFRAG=y parameter fails to clear IP reassembly state after delivering a complete datagram. An attacker who can deliver fragmented IP traffic can execute arbitrary code by sending duplicated last-fragment IP packets. This issue was fixed in commit…
When was CVE-2026-15390 made public?
CVE-2026-15390 was made public on September 29, 2026: that is the date its CVE record's CNA, CERT.PL, gives for when the vulnerability was made public. The CVE record itself was published on September 29, 2026. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-15390 actively exploited?
CVE-2026-15390 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15390?
CVE-2026-15390 has a CVSS base score of 9.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15390?
A fix for CVE-2026-15390 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-15390 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-2026-15390

Explore →

Is Your Infrastructure Affected by CVE-2026-15390?

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