Skip to content
Systems

CVE-2026-29009

HIGH
High
EPSS 0.74%Jul 9, 2026

Buffer overflow in U-Boot NFS READLINK handling allows remote memory corruption.

common questions

Is CVE-2026-29009 being exploited?

Not confirmed. CVE-2026-29009 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.74% probability of exploitation in the next 30 days.

How severe is CVE-2026-29009?

CVE-2026-29009 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-29009?

Not known from our data. No patch reference has been recorded for CVE-2026-29009, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-29009 affect?

CVE-2026-29009 affects U-Boot (<= 2026.04-rc3) with CONFIG_CMD_NFS enabled, Embedded/network-booted devices using U-Boot NFS client. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-29009?

Disable CONFIG_CMD_NFS or block untrusted NFS servers; apply vendor/U-Boot patch when released.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
U-Boot (<= 2026.04-rc3) with CONFIG_CMD_NFS enabledEmbedded/network-booted devices using U-Boot NFS client
impact

Remote memory corruption via malicious NFS READLINK responses; can corrupt NFS client state and enable takeover of the client.

action required

Immediate action required

affected versions
u-boot u-boot
  • affected< 2026.07-rc2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free