Vulnerabilities / CVE-2026-34987

critical

CVE-2026-34987

wasmtime: bytecodealliance/wasmtime: Wasmtime: Arbitrary code execution via incorrect memory offset handling in Winch compiler

Published Modified CWE 125, 787
In the Trivy database since at least 24 Oct 2026, 07:11 UTCWhen it arrived before that build is not recorded.

Severity by source

NVD9.9CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GHSA9.2CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Red Hat8.5CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
Julia9.0CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Trivy's own label is CRITICAL. Rated critical by NVD, GHSA, Julia. Rated lower by Red Hat (high).

Description

Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, 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. This vulnerability is fixed in 36.0.7, 42.0.2, and 43.0.1.

Affected packages and fixed versions

SourcePackageFixed in
cargo::GitHub Security Advisory Rustwasmtime36.0.7, 42.0.2, 43.0.1
julia::Julia Ecosystem Security AdvisoriesWasmtime_jll45.0.1+0
chainguardwasmcloud, wizer, yara-x and 1 more2.0.4-r0 and 3 more
debian 13rust-wasmtimeno fix listed
debian 14rust-wasmtime36.0.7+dfsg-1
echorust-wasmtimeno fix listed
rapidfort debian 12rust-wasmtime0:36.0.7+dfsg-1
rapidfort debian 13rust-wasmtime0:36.0.7+dfsg-1
wolfiwasmcloud, wizer, yara-x and 1 more2.0.4-r0 and 3 more
Show all 15 entries from 9 sources
SourcePackageFixed in
cargo::GitHub Security Advisory Rustwasmtime36.0.7, 42.0.2, 43.0.1
julia::Julia Ecosystem Security AdvisoriesWasmtime_jll45.0.1+0
chainguardwasmcloud2.0.4-r0
chainguardwizer11.0.3-r10
chainguardyara-x1.15.0-r2
chainguardzed0.228.0-r3
debian 13rust-wasmtimeno fix listed
debian 14rust-wasmtime36.0.7+dfsg-1
echorust-wasmtimeno fix listed
rapidfort debian 12rust-wasmtime0:36.0.7+dfsg-1
rapidfort debian 13rust-wasmtime0:36.0.7+dfsg-1
wolfiwasmcloud2.0.4-r0
wolfiwizer11.0.3-r10
wolfiyara-x1.15.0-r2
wolfized0.228.0-r3

References

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.