CVE-2026-71971

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — 5 sources updated this week
8.2EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.2Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then 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.2HIGHhigh confidence
EG Risk
52
EG Risk 52/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
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.
EPSS PROB
0.4%
EPSS %ILE
29th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 (4)

Auto-updated Sep 29, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

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
generic

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

https://github.com/u-boot/u-boot
generic

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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 25× in last 7d / 25× 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 04:06 UTCVendor advisory
  2. 2026-10-04 04:06 UTCGHSA enrichment
  3. 2026-10-03 16:15 UTCEG score recompute
  4. 2026-10-03 16:15 UTCVendor advisory
  5. 2026-10-03 16:15 UTCGHSA enrichment
  6. 2026-10-03 14:26 UTCEPSS rescore
  7. 2026-10-03 04:25 UTCEG score recompute
  8. 2026-10-03 04:25 UTCGHSA enrichment
  9. 2026-10-02 16:34 UTCGHSA enrichment
  10. 2026-10-02 04:43 UTCEG score recompute
  11. 2026-10-02 04:43 UTCGHSA enrichment
  12. 2026-10-01 19:50 UTCEPSS rescore
  13. 2026-10-01 16:51 UTCGHSA enrichment
  14. 2026-10-01 04:38 UTCGHSA enrichment
  15. 2026-09-30 16:45 UTCGHSA enrichment
  16. 2026-09-30 15:38 UTCEG score recompute
  17. 2026-09-30 15:38 UTCGHSA enrichment
  18. 2026-09-30 15:03 UTCEPSS rescore
  19. 2026-09-30 14:31 UTCEG score recompute
  20. 2026-09-30 14:31 UTCGHSA enrichment
  21. 2026-09-30 10:16 UTCEG score recompute
  22. 2026-09-30 10:16 UTCGHSA enrichment
  23. 2026-09-29 22:25 UTCEG score recompute
  24. 2026-09-29 21:37 UTCEG score recompute
  25. 2026-09-29 21:33 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-71971?
CVE-2026-71971 is a high vulnerability published on September 29, 2026. U-Boot before 2026.10-rc3 with CONFIGIPDEFRAG 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…
When was CVE-2026-71971 disclosed?
CVE-2026-71971 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-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 (29th 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?
An upstream fix for CVE-2026-71971 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-71971 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Book a Demo →Browse All CVEs