CVE-2026-115384

validatingZero is analyzing and reversing it now.

GHSA-6fff-wrjr-wjxr ↗

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.
bytecodealliance wasmtime
ETK-2026-2510Zero's internal tracking ID, independent of the CVE number., permanent identifier
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal (cve.org) +0h
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Wasmtime versions 39.0.0 through 48.0.3 and 49.0.0 through 49.0.1 are affected by a native-stack buffer overflow in component-model asynchronous callback handling. A malicious guest component may crash the host or break out of the WebAssembly sandbox when it can invoke an async callback with mismatched result types.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Upgrade Wasmtime 39.x through 48.x to 48.0.4 or later, and upgrade 49.0.0 or 49.0.1 to 49.0.2 or later. Until upgraded, do not run untrusted components that use component-model async callbacks.

check
building now
exploit
not yet
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.
–
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
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 19:13Z
Δ 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

Run in progress: no artifact yet.

source signals

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

  1. 2026-10-22 19:13Z
    ghsa: trigger signal, started the run
  2. 2026-10-22 19:13Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2510",
  "cve_id": "CVE-2026-115384",
  "display_id": "CVE-2026-115384",
  "ghsa_id": "GHSA-6fff-wrjr-wjxr",
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "anchored",
  "title": "Stack buffer overflow in Wasmtime async callbacks",
  "summary": "Wasmtime versions 39.0.0 through 48.0.3 and 49.0.0 through 49.0.1 are affected by a native-stack buffer overflow in component-model asynchronous callback handling. A malicious guest component may crash the host or break out of the WebAssembly sandbox when it can invoke an async callback with mismatched result types.",
  "mitigation": "Upgrade Wasmtime 39.x through 48.x to 48.0.4 or later, and upgrade 49.0.0 or 49.0.1 to 49.0.2 or later. Until upgraded, do not run untrusted components that use component-model async callbacks.",
  "vendor": "bytecodealliance",
  "product": "wasmtime",
  "affected": [],
  "cwes": null,
  "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": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": "2026-10-22T19:13:51.422000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T19:13:51.422000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T19:13:51.422000+00:00",
      "url": "https://github.com/advisories/GHSA-6fff-wrjr-wjxr"
    }
  }
}

published 2026-10-22 21:48Z
last change 2026-10-22 21:48Z

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.