CVE-2026-74222

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

GHSA-fm4f-g9jh-3qfq ↗EUVD-2026-89435 ↗

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-416 Use After Free
ETK-2026-24, permanent identifier
6d 05h 31msince last run
23mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+363h04m
0
+2h
+4h
+6h
+8h
+10h

description

U-Boot versions before 2026.10-rc5 are affected in the lwIP wget receive path. Processing HTTP data when local storage fails can cause use of released connection state and crash the bootloader. Exposure requires the affected lwIP wget functionality to process such HTTP traffic.

mitigation

Upgrade U-Boot to version 2026.10-rc5 or a later release. Until upgraded, disable or avoid the affected lwIP wget path where operationally feasible.

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.30%21st percentile
agent run time
23m
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-74222

{
  "etk_id": "ETK-2026-24",
  "cve_id": "CVE-2026-74222",
  "display_id": "CVE-2026-74222",
  "ghsa_id": "GHSA-fm4f-g9jh-3qfq",
  "euvd_id": "EUVD-2026-89435",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Use-after-free in U-Boot lwIP wget handling",
  "summary": "U-Boot versions before 2026.10-rc5 are affected in the lwIP wget receive path. Processing HTTP data when local storage fails can cause use of released connection state and crash the bootloader. Exposure requires the affected lwIP wget functionality to process such HTTP traffic.",
  "mitigation": "Upgrade U-Boot to version 2026.10-rc5 or a later release. Until upgraded, disable or avoid the affected lwIP wget path where operationally feasible.",
  "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": [
    416
  ],
  "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.003,
  "epss_percentile": 0.2165,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 22.767205133333334,
  "t0_at": "2026-09-29T21:29:23.960000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-29T21:29:23.960000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-29T21:29:23.960000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-74222"
    }
  }
}

published 2026-09-29 22:12Z
last change 2026-10-21 05:31Z

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.