CVE-2026-29009

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.7% (53rd percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.2 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-07-08) is not newer than that change (2026-07-24), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan mitigationRemediate 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 referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

U-Boot before 2026.07-rc2 contains a buffer overflow vulnerability in nfs_readlink_reply() (net/nfs-common.c) when CONFIG_CMD_NFS is enabled, allowing a malicious or compromised NFS server to overflow the 2048-byte nfs_path_buff buffer by returning multiple relative symlink targets that are appended without cumulative length validation. Attackers can send two or more READLINK responses containing relative symlink targets of approximately 1100 bytes each to corrupt adjacent BSS variables including nfs_server_ip, nfs_server_mount_port, nfs_server_port, nfs_our_port, nfs_state, and rpc_id, potentially achieving memory corruption and control over the NFS client state machine.

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 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 (value × EchelonGraph’s weight)
Severity98% × 45%
The EG Score, 9.8 of 10.
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 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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

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.

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

July 8, 2026

Last Modified

July 24, 2026

Advisory Details (6)

Auto-updated Oct 10, 2026
Fix referenced — no release confirmed yet.
Web page

U-Boot TCP/NFS Vulnerabilities: Integer Underflow and Buffer Overflow in the World’s Most Popular Bootloader

https://y637f9qq2x.com/posts/u-boot-tcp-nfs-vulns/
Web page

U-Boot < 2026.07-rc2 Buffer Overflow in nfs_readlink_reply() via NFS READLINK | Advisories | VulnCheck

https://www.vulncheck.com/advisories/u-boot-rc3-buffer-overflow-in-nfs-readlink-reply-via-nfs-readlink
Web page

U-Boot – deinde.dev

https://u-boot.org/
Web page

U-Boot v2026.07-rc2 · u-boot / U-Boot · GitLab

https://git.u-boot-project.org/u-boot/u-boot/-/releases/v2026.07-rc2
Web page

net: nfs: fix buffer overflow in nfs_readlink_reply() (d6694018) · Commits · u-boot / U-Boot · GitLab

https://git.u-boot-project.org/u-boot/u-boot/-/commit/d6694018eaddefac6aae974f9cec72fd6e58f1bc
Web page

Coordinated Vulnerability Disclosure - U-Boot Multiple Vulnerabilities (3)

https://lists.denx.de/pipermail/u-boot/2026-May/617853.html

Vendor Advisories for CVE-2026-29009(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
u-boot2021.01+dfsg-5 ... 2025.01-3.2 (53 versions)
  • every version on: no fix on record
—
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.

Data Freshness Timeline

(refreshed 17× 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 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 96 of 364 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 268 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-29009?
CVE-2026-29009 is a critical-severity vulnerability; its CVE record was published on July 8, 2026. U-Boot before 2026.07-rc2 contains a buffer overflow vulnerability in nfsreadlinkreply() (net/nfs-common.c) when CONFIGCMDNFS is enabled, allowing a malicious or compromised NFS server to overflow the 2048-byte nfspathbuff buffer by returning multiple relative symlink targets that are appended…
When was CVE-2026-29009 made public?
CVE-2026-29009 was made public on May 8, 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 July 8, 2026. EchelonGraph's copy of the record carries a last-modified date of July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-29009 actively exploited?
CVE-2026-29009 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-29009?
CVE-2026-29009 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-29009?
A fix for CVE-2026-29009 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-29009 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-29009

Explore →

Is Your Infrastructure Affected by CVE-2026-29009?

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

Book a Demo →Browse All CVEs