CVE-2026-115893

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

GHSA-mghf-wjfp-p5xm ↗EUVD-2026-109188 ↗

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.
rust wasmtime <36.0.19; >=37.0.0; <48.0.7; >=49.0.0; <49.0.4
fixed in 36.0.19, 48.0.7, 49.0.4
CWE-691 Insufficient Control Flow Management
ETK-2026-2280Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:cargo/wasmtime
5h 54msince last run
22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0dcve.org publication+4.1dwaiting for further signals+4.8d
0
+1d
+2d
+3d

description

Wasmtime deployments on AArch64 that use the default Cranelift backend are affected by a control-flow compilation flaw. An attacker who can submit a WebAssembly module may be able to execute outside the intended Wasm sandbox.

mitigation

Upgrade wasmtime to 36.0.19, 48.0.7, 49.0.4 or later.

fixed in 36.0.19, 48.0.7, 49.0.4

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-23 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-10-19 19:21Z
  2. 2026-10-23 21:29Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2280",
  "cve_id": "CVE-2026-115893",
  "display_id": "CVE-2026-115893",
  "ghsa_id": "GHSA-mghf-wjfp-p5xm",
  "euvd_id": "EUVD-2026-109188",
  "status": "published",
  "anchor_state": "anchored",
  "title": "AArch64 sandbox escape from Wasmtime branch miscompilation",
  "summary": "Wasmtime deployments on AArch64 that use the default Cranelift backend are affected by a control-flow compilation flaw. An attacker who can submit a WebAssembly module may be able to execute outside the intended Wasm sandbox.",
  "mitigation": "Upgrade wasmtime to 36.0.19, 48.0.7, 49.0.4 or later.",
  "vendor": "rust",
  "product": "wasmtime",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<36.0.19",
        ">=37.0.0",
        "<48.0.7",
        ">=49.0.0",
        "<49.0.4"
      ],
      "ecosystem": "rust",
      "fixed_versions": [
        "36.0.19",
        "48.0.7",
        "49.0.4"
      ],
      "package_name": "wasmtime",
      "purl": "pkg:cargo/wasmtime"
    }
  ],
  "cwes": [
    691
  ],
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 21.872882866666668,
  "t0_at": "2026-10-23T21:29:33.917000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T19:21:02+00:00",
      "days": -4.089258298611111,
      "is_lower_bound": false,
      "measured_at": "2026-10-23T21:29:33.917000+00:00",
      "url": "https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-mghf-wjfp-p5xm"
    }
  }
}

published 2026-10-21 03:54Z
last change 2026-10-24 20:19Z

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.