Advisory record · GHSA-xx5w-cvp6-jv83

Wasmtime with Winch compiler backend may allow a sandbox-escaping memory access

CVSS 9.0 CriticalCriticalEPSS 0.0028 · 21st percentile

Critical, because:

  • CVSS score 9.0: 9.0 or more.

How we decide what’s critical

Published by the maintainers · not yet reviewed by GitHub. The bytecodealliance/wasmtime maintainers published this as a GitHub repository advisory; GitHub’s reviewed advisory replaces it here when it arrives.

Published by the bytecodealliance/wasmtime maintainers at 9 Apr 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
wasmtimecrates.io>=0.0.0-0, <36.0.7 || >=37.0.0, <42.0.2 || >=43.0.0, <43.0.136.0.7, 42.0.2, 43.0.1
Identifiers
GHSA-xx5w-cvp6-jv83 · CVE-2026-34987 · RUSTSEC-2026-0095
Weakness (CWE)
CWE-125 · CWE-787
Published
9 Apr 2026
Updated
12 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Wasmtime, when built with the Winch compiler backend, is affected in versions before 36.0.7, from 37.0.0 before 42.0.2, and from 43.0.0 before 43.0.1. The source gives few details about the attack, but it describes a sandbox-escaping memory access. Upgrade to 36.0.7, 42.0.2, or 43.0.1, depending on your release line.

Written 3 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.0 Critical 4.0 CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0028, the 21st percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 9 Apr 2026, 16:51 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:24 UTC First seen by agentprime
  3. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.