CVE-2026-34987: Wasmtime Wasmtime With Winch Compiler Backend Vulnerability

CRITICAL
Advisory Identifier: GHSA-xx5w-cvp6-jv83
CWE-125 CWE-787
Published
Advisory Summary

CVE-2026-34987 is a CRITICAL wasmtime with winch compiler backend vulnerability (CWE-125: Out-of-bounds Read) affecting Wasmtime libraries in the crates.io ecosystem. The issue involves wasmtime with winch compiler backend on aarch64 may allow a sandbox-escaping memory access. Remediation is available by upgrading affected packages to version 36.0.7, 42.0.2, 43.0.1.

CVE-2026-34987 at a Glance

CVE Identifier CVE-2026-34987
GHSA Identifier GHSA-xx5w-cvp6-jv83
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-125: Out-of-bounds Read
Affected Product Wasmtime
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix CVE-2026-34987

To remediate this vulnerability, upgrade all affected Wasmtime dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

wasmtime fixed: 36.0.7
Upgrade wasmtime to 36.0.7
wasmtime fixed: 42.0.2
Upgrade wasmtime to 42.0.2
wasmtime fixed: 43.0.1
Upgrade wasmtime to 43.0.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for wasmtime

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-34987, inspect your project dependencies for Wasmtime:

inspect dependencies for wasmtime

Analyze the terminal output to locate any version of Wasmtime in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 36.0.7), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-125: Out-of-bounds Read, where the product reads data past the end, or before the beginning, of the intended buffer. In Wasmtime, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Wasmtime with its Winch (baseline) non-default compiler backend may allow properly constructed guest Wasm to access host memory outside of its linear-memory sandbox. This vulnerability requires use of the Winch compiler (`-Ccompiler=winch`). By default, Wasmtime uses its Cranelift backend, not Winch. With Winch, the same incorrect assumption is present in theory on both aarch64 and x86-64. The aarch64 case has an observed-working proof of concept, while the x86-64 case is theoretical and may not be reachable in practice. This Winch compiler bug can allow the Wasm guest to access memory before or after the linear-memory region, independently of whether pre- or post-guard regions are configured. The accessible range in the initial bug proof-of-concept is up to 32KiB before the start of memory, or ~4GiB after the start of memory, independently of the size of pre- or post-guard regions or the use of explicit or guard-region-based bounds checking. However, the underlying bug assumes a 32-bit memory offset stored in a 64-bit register has its upper bits cleared when it may not, and so closely related variants of the initial proof-of-concept may be able to access truly arbitrary memory in-process. This could result in a host process segmentation fault (DoS), an arbitrary data leak from the host process, or with a write, potentially an arbitrary RCE. ### Patches Wasmtime 43.0.1, 42.0.2, and 36.0.7 have been released with fixes for this issue. ### Workaround There are no workarounds within the Winch compiler backend while using the affected versions. Users of Wasmtime are encouraged either to upgrade to patched versions or, if that is not possible, use the Cranelift compiler backend.

CVE-2026-34987 Affected Wasmtime Versions

3 component(s)
Fixed Versions:
36.0.742.0.243.0.1
Product / Package Ecosystem Affected Versions Fixed Version
wasmtime
crates.io
≥ 25.0.0
< 36.0.7
36.0.7
wasmtime
crates.io
≥ 37.0.0
< 42.0.2
42.0.2
wasmtime
crates.io
≥ 43.0.0
< 43.0.1
All 1 versions
43.0.0
43.0.1

References

Frequently Asked Questions

What is CVE-2026-34987?
CVE-2026-34987 is a security vulnerability in Wasmtime involving Wasmtime with Winch compiler backend on aarch64 may allow a sandbox-escaping memory access under CWE-125: Out-of-bounds Read.
Which Wasmtime versions are affected?
Affected versions include releases prior to 36.0.7, 42.0.2, 43.0.1 across affected packages: wasmtime.
What version fixes CVE-2026-34987?
Upgrading to 36.0.7, 42.0.2, 43.0.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is wasmtime affected?
Yes, wasmtime is affected in releases prior to 36.0.7, 42.0.2, 43.0.1. Upgrade your dependency to 36.0.7, 42.0.2, 43.0.1 or later.
What CWE is associated with CVE-2026-34987?
CVE-2026-34987 is classified under CWE-125: Out-of-bounds Read (The product reads data past the end, or before the beginning, of the intended buffer.).
How can I check crates.io dependencies for CVE-2026-34987?
Run the dependency tree command: 'inspect dependencies for wasmtime'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xx5w-cvp6-jv83",
  "modified" : "2026-04-10T15:31:18Z",
  "published" : "2026-04-10T15:31:18Z",
  "aliases" : [ "CVE-2026-34987" ],
  "summary" : "Wasmtime with Winch compiler backend on aarch64 may allow a sandbox-escaping memory access",
  "details" : "### Impact\n\nWasmtime with its Winch (baseline) non-default compiler backend may allow properly constructed guest Wasm to access host memory outside of its linear-memory sandbox.\n\nThis vulnerability requires use of the Winch compiler (`-Ccompiler=winch`). By default, Wasmtime uses its Cranelift backend, not Winch. With Winch, the same incorrect assumption is present in theory on both aarch64 and x86-64. The aarch64 case has an observed-working proof of concept, while the x86-64 case is theoretical and may not be reachable in practice.\n\nThis Winch compiler bug can allow the Wasm guest to access memory before or after the linear-memory region, independently of whether pre- or post-guard regions are configured. The accessible range in the initial bug proof-of-concept is up to 32KiB before the start of memory, or ~4GiB after the start of memory, independently of the size of pre- or post-guard regions or the use of explicit or guard-region-based bounds checking. However, the underlying bug assumes a 32-bit memory offset stored in a 64-bit register has its upper bits cleared when it may not, and so closely related variants of the initial proof-of-concept may be able to access truly arbitrary memory in-process. This could result in a host process segmentation fault (DoS), an arbitrary data leak from the host process, or with a write, potentially an arbitrary RCE.\n\n### Patches\n\nWasmtime 43.0.1, 42.0.2, and 36.0.7 have been released with fixes for this issue.\n\n### Workaround\n\nThere are no workarounds within the Winch compiler backend while using the affected versions. Users of Wasmtime are encouraged either to upgrade to patched versions or, if that is not possible, use the Cranelift compiler backend.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "wasmtime"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "25.0.0"
      }, {
        "fixed" : "36.0.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "wasmtime"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "37.0.0"
      }, {
        "fixed" : "42.0.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "wasmtime"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "43.0.0"
      }, {
        "fixed" : "43.0.1"
      } ]
    } ],
    "versions" : [ "43.0.0" ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-xx5w-cvp6-jv83"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34987"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/bytecodealliance/wasmtime"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2026-0095.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-125", "CWE-787" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-10T15:31:18Z",
    "nvd_published_at" : "2026-04-09T19:16:25Z"
  }
}