CVE-2026-74221

waiting for further signalsZero needs more public information before it can validate it.

GHSA-r9ch-9wx4-f978 ↗EUVD-2026-89434 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
u-boot < 2026.10-rc5
fixed in 2026.10-rc5
CWE-195 Signed to Unsigned Conversion Error
ETK-2026-25, permanent identifier
6d 06h 24msince last run
32mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+363h16m
0
+2h
+4h
+6h
+8h
+10h

description

U-Boot versions before 2026.10-rc5 are affected by a buffer overflow while handling NFS READLINK responses. A malicious or compromised NFS server can corrupt bootloader memory and cause a crash when U-Boot processes a malformed reply; exposure requires U-Boot to communicate with that server for NFS operations.

mitigation

Upgrade U-Boot to 2026.10-rc5 or later. Until upgrades are complete, restrict boot-time NFS access to trusted, authenticated network paths and servers.

fixed in 2026.10-rc5

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.34%26th percentile
agent run time
32m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-29 21:29Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-29 21:29Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-74221

{
  "etk_id": "ETK-2026-25",
  "cve_id": "CVE-2026-74221",
  "display_id": "CVE-2026-74221",
  "ghsa_id": "GHSA-r9ch-9wx4-f978",
  "euvd_id": "EUVD-2026-89434",
  "status": "published",
  "anchor_state": "anchored",
  "title": "U-Boot NFS reply buffer overflow",
  "summary": "U-Boot versions before 2026.10-rc5 are affected by a buffer overflow while handling NFS READLINK responses. A malicious or compromised NFS server can corrupt bootloader memory and cause a crash when U-Boot processes a malformed reply; exposure requires U-Boot to communicate with that server for NFS operations.",
  "mitigation": "Upgrade U-Boot to 2026.10-rc5 or later. Until upgrades are complete, restrict boot-time NFS access to trusted, authenticated network paths and servers.",
  "vendor": "u-boot",
  "product": "u-boot",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2026.10-rc5"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2026.10-rc5"
      ],
      "package_name": "u-boot",
      "purl": null
    }
  ],
  "cwes": [
    195
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0034,
  "epss_percentile": 0.2646,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 31.848561216666667,
  "t0_at": "2026-09-29T21:29:23.283000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-29T21:29:23.283000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-29T21:29:23.283000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-74221"
    }
  }
}

published 2026-09-29 22:14Z
last change 2026-10-21 07:03Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.