CVE-2026-15390

CRITICALPre-NVD 9.09.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (19th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 5 sources updated this week
9.0EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.0Exploit: None knownExposed services: Not assessed

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

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 v3
9.0
EG Score
9.0CRITICALmedium confidence
EG Risk
41
EG Risk 41/100CISA SSVC

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 computed
Severity90% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
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.3%
EPSS %ILE
19th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 29, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 29, 2026
No patch confirmed yet.
generic

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
generic

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.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 54× in last 7d / 54× 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.

  1. 2026-10-04 12:42 UTCVendor advisory
  2. 2026-10-04 12:42 UTCGHSA enrichment
  3. 2026-10-04 09:01 UTCVendor advisory
  4. 2026-10-04 09:01 UTCGHSA enrichment
  5. 2026-10-04 05:19 UTCVendor advisory
  6. 2026-10-04 05:19 UTCGHSA enrichment
  7. 2026-10-04 01:39 UTCVendor advisory
  8. 2026-10-04 01:38 UTCGHSA enrichment
  9. 2026-10-03 21:55 UTCVendor advisory
  10. 2026-10-03 21:55 UTCGHSA enrichment
  11. 2026-10-03 18:09 UTCVendor advisory
  12. 2026-10-03 18:08 UTCGHSA enrichment
  13. 2026-10-03 14:25 UTCEG score recompute
  14. 2026-10-03 14:25 UTCVendor advisory
  15. 2026-10-03 14:25 UTCGHSA enrichment
  16. 2026-10-03 14:25 UTCEPSS rescore
  17. 2026-10-03 10:41 UTCVendor advisory
  18. 2026-10-03 10:41 UTCGHSA enrichment
  19. 2026-10-03 07:00 UTCGHSA enrichment
  20. 2026-10-03 03:19 UTCGHSA enrichment
  21. 2026-10-02 23:38 UTCGHSA enrichment
  22. 2026-10-02 19:56 UTCEG score recompute
  23. 2026-10-02 19:56 UTCGHSA enrichment
  24. 2026-10-02 16:15 UTCGHSA enrichment
  25. 2026-10-02 16:15 UTCGHSA enrichment
Show 29 more
  1. 2026-10-02 16:15 UTCGHSA enrichment
  2. 2026-10-02 12:29 UTCGHSA enrichment
  3. 2026-10-02 08:48 UTCGHSA enrichment
  4. 2026-10-02 05:06 UTCGHSA enrichment
  5. 2026-10-02 01:25 UTCGHSA enrichment
  6. 2026-10-01 21:44 UTCEG score recompute
  7. 2026-10-01 21:43 UTCGHSA enrichment
  8. 2026-10-01 19:49 UTCEPSS rescore
  9. 2026-10-01 18:00 UTCGHSA enrichment
  10. 2026-10-01 14:15 UTCGHSA enrichment
  11. 2026-10-01 10:34 UTCGHSA enrichment
  12. 2026-10-01 06:51 UTCGHSA enrichment
  13. 2026-10-01 03:10 UTCGHSA enrichment
  14. 2026-09-30 23:29 UTCGHSA enrichment
  15. 2026-09-30 19:45 UTCGHSA enrichment
  16. 2026-09-30 18:17 UTCEG score recompute
  17. 2026-09-30 18:17 UTCGHSA enrichment
  18. 2026-09-30 15:02 UTCEPSS rescore
  19. 2026-09-30 14:36 UTCGHSA enrichment
  20. 2026-09-30 10:51 UTCGHSA enrichment
  21. 2026-09-30 07:09 UTCGHSA enrichment
  22. 2026-09-30 03:27 UTCGHSA enrichment
  23. 2026-09-29 23:45 UTCGHSA enrichment
  24. 2026-09-29 18:58 UTCGHSA enrichment
  25. 2026-09-29 15:13 UTCGHSA enrichment
  26. 2026-09-29 11:32 UTCEG score recompute
  27. 2026-09-29 11:04 UTCEG score recompute
  28. 2026-09-29 10:21 UTCEG score recompute
  29. 2026-09-29 10:18 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15390?
CVE-2026-15390 is a critical vulnerability published on September 29, 2026. Das U-Boot with CONFIGIPDEFRAG=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 disclosed?
CVE-2026-15390 was first published on September 29, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15390 actively exploited?
CVE-2026-15390 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (19th 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?
No fix for CVE-2026-15390 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-2026-15390 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.