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

validatedZero produced an exploit or a check.

GHSA-f2pq-268w-886c ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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-wasi <36.0.22; >=37.0.0; <48.0.10; >=49.0.0; <49.0.7; >=50.0.0; <50.0.3
fixed in 36.0.22, 48.0.10, 49.0.7, 50.0.3
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-4991Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:cargo/wasmtime-wasi
−6h42mTTV
36mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org, not yet published
trigger signal −13h01mcheck available−6h42magent stopped
−12h
−9h
−6h
−3h
0

description

On Windows hosts, wasmtime-wasi can allow a guest with access to a preopened directory to access files and directories outside its filesystem sandbox. The guest may read host-accessible files and, when granted writable directory access, may also create, modify, or delete host-accessible files.

mitigation

Upgrade wasmtime-wasi to 36.0.22, 48.0.10, 49.0.7, or 50.0.3, as appropriate for your release line. Until upgraded, do not run untrusted guests on Windows with preopened directories, especially writable ones.

fixed in 36.0.22, 48.0.10, 49.0.7, 50.0.3

check
available
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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
36m
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 check: a technique exists and was validated, 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-11-19 19:53Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4991",
  "cve_id": null,
  "display_id": "ETK-2026-4991",
  "ghsa_id": "GHSA-f2pq-268w-886c",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Windows filesystem sandbox escape in wasmtime-wasi",
  "summary": "On Windows hosts, `wasmtime-wasi` can allow a guest with access to a preopened directory to access files and directories outside its filesystem sandbox. The guest may read host-accessible files and, when granted writable directory access, may also create, modify, or delete host-accessible files.",
  "mitigation": "Upgrade `wasmtime-wasi` to 36.0.22, 48.0.10, 49.0.7, or 50.0.3, as appropriate for your release line. Until upgraded, do not run untrusted guests on Windows with preopened directories, especially writable ones.",
  "vendor": "rust",
  "product": "rust:wasmtime-wasi",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<36.0.22"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "36.0.22"
      ],
      "package_name": "wasmtime-wasi",
      "purl": "pkg:cargo/wasmtime-wasi"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">=37.0.0",
        "<48.0.10"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "48.0.10"
      ],
      "package_name": "wasmtime-wasi",
      "purl": "pkg:cargo/wasmtime-wasi"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">=49.0.0",
        "<49.0.7"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "49.0.7"
      ],
      "package_name": "wasmtime-wasi",
      "purl": "pkg:cargo/wasmtime-wasi"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">=50.0.0",
        "<50.0.3"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "50.0.3"
      ],
      "package_name": "wasmtime-wasi",
      "purl": "pkg:cargo/wasmtime-wasi"
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 36.3100997,
  "t0_at": null,
  "signals": {
    "check": {
      "at": "2026-11-20T02:12:48.366325+00:00",
      "days": -0.2789271250115741,
      "is_lower_bound": true,
      "measured_at": "2026-11-20T08:54:28.146964+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-11-19T19:53:19+00:00",
      "days": -0.5424614574768518,
      "is_lower_bound": true,
      "measured_at": "2026-11-20T08:54:28.146964+00:00",
      "url": "https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-f2pq-268w-886c"
    }
  }
}

published 2026-11-20 01:36Z
last change 2026-11-20 08:51Z

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.