CVE-2026-71971

HIGHPre-NVD 8.28.2
EchelonGraph scoreMEDIUM confidence

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

Score 8.2 from GitHub Security Advisory (severity: HIGH) published 2026-09-30. A secondary CVSS source baseline 8.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-89429 (ENISA EUVD) · GHSA-9gg4-qrm6-f795 (GitHub Security Advisories)Source: ENISA EUVD

8.2EG
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.4%CVSS: 8.2Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

U-Boot before 2026.10-rc3 with CONFIG_IP_DEFRAG enabled contains an out-of-bounds write vulnerability in the __net_defragment() function in net/net.c. Remote attackers can send a crafted IP fragment with non-zero offset and More-Fragments flag set during netboot to corrupt adjacent memory and crash the bootloader.

CVSS v3
8.2
EG Score
8.2HIGHmedium confidence
EG Risk
52
EG Risk 52/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)
Severity82% × 45%
Impact severity (EG Severity): CVSS 8.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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 partial (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.4%
EPSS %ILE
32nd
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.2): severity, escalated by confirmed exploitation. This CVE's 8.2 is its impact severity (EG Severity), not escalated.

EG Severity
8.2 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-19). 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: 14 days if the affected system is publicly exposed; 60 days 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; 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 partial (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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 (4)

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

U-Boot before 2026.10-rc3 Out-of-Bounds Write in IP Fragment Reassembly | Advisories | VulnCheck

https://www.vulncheck.com/advisories/u-boot-before-2026.10-rc3-out-of-bounds-write-in-ip-fragment-reassembly
Web page

GitHub - u-boot/u-boot: "Das U-Boot" Source Tree · GitHub

https://github.com/u-boot/u-boot
Web page

u-boot/net/net.c at v2026.07 · u-boot/u-boot · GitHub

https://github.com/u-boot/u-boot/blob/v2026.07/net/net.c#L975
GitHub commit

commit 04ca915d5bf3 (u-boot/u-boot)

Fix landed in u-boot/u-boot commit 04ca915d5bf3 — awaiting tagged release

https://github.com/u-boot/u-boot/commit/04ca915d5bf39dda5d1bce62d04d2b59d293c5b9

Vendor Advisories for CVE-2026-71971(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-18ubuntu

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(1)

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 12× in last 7d / 43× 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 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). "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 143 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 43 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-71971?
CVE-2026-71971 is a high-severity vulnerability; its CVE record was published on September 29, 2026. U-Boot before 2026.10-rc3 with CONFIG_IP_DEFRAG enabled contains an out-of-bounds write vulnerability in the __net_defragment() function in net/net.c. Remote attackers can send a crafted IP fragment with non-zero offset and More-Fragments flag set during netboot to corrupt adjacent memory and crash…
When was CVE-2026-71971 made public?
CVE-2026-71971 was made public on July 28, 2026: that is the date its CVE record's CNA, VulnCheck, 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-71971 actively exploited?
CVE-2026-71971 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-71971?
CVE-2026-71971 has a CVSS base score of 8.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-71971?
A fix for CVE-2026-71971 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-71971 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-71971

Explore →

Is Your Infrastructure Affected by CVE-2026-71971?

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