ETK-2026-467Zero's internal tracking ID, independent of the CVE number.

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

GHSA-32h6-97mm-8q3c ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
rust:wasmtime >= 39.0.0, < 48.0.4; >= 49.0.0, < 49.0.2
fixed in 48.0.4, 49.0.2
CWE-20 Improper Input Validation
ETK-2026-467, no cve assigned
pkg:cargo/wasmtime
18d 04h 58msince last run
52mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −19dwaiting for further signals−18d
−15d
−10d
−5d
0

description

Wasmtime with component-model-async enabled may accept components whose async callback signatures are invalid. An attacker able to submit a malformed component could corrupt the native stack, potentially causing a process crash or escaping the WebAssembly sandbox to affect host code.

mitigation

Upgrade wasmtime to 48.0.4, 49.0.2 or later.

fixed in 48.0.4, 49.0.2

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.
–
agent run time
52m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ 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-10-02 19:39Z

this entry in the feed

GET /api/v1/feed/ETK-2026-467

{
  "etk_id": "ETK-2026-467",
  "cve_id": null,
  "display_id": "ETK-2026-467",
  "ghsa_id": "GHSA-32h6-97mm-8q3c",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Callback type validation flaw in Wasmtime async components",
  "summary": "Wasmtime with component-model-async enabled may accept components whose async callback signatures are invalid. An attacker able to submit a malformed component could corrupt the native stack, potentially causing a process crash or escaping the WebAssembly sandbox to affect host code.",
  "mitigation": "Upgrade wasmtime to 48.0.4, 49.0.2 or later.",
  "vendor": "rust",
  "product": "rust:wasmtime",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 39.0.0, < 48.0.4",
        ">= 49.0.0, < 49.0.2"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "48.0.4",
        "49.0.2"
      ],
      "package_name": "wasmtime",
      "purl": "pkg:cargo/wasmtime"
    }
  ],
  "cwes": [
    20
  ],
  "cvss_score": 9.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:H/SC:L/SI:H/SA:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 51.81995375,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-10-02T19:39:24+00:00",
      "days": -19.005830011759258,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T19:47:47.736475+00:00",
      "url": "https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-32h6-97mm-8q3c"
    }
  }
}

published 2026-10-03 15:00Z
last change 2026-10-21 19:22Z

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.