CRITICALVulnerability
Verified
Global

NVD CRITICAL: CVE-2026-34987 — Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and...

·Source: NIST NVD

Updated:

Executive Summary

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,

Analysis

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. CVSS Score: 9.9. Published: 2026-04-09T19:16:25.000.

Indicators of Compromise (1)

CVE (1)
CVE-2026-34987
Source Attribution

Originally published by NIST NVD on Apr 9, 2026. Verified by: NIST.

Related Threats

LOWVulnerability

Weekly Metasploit Update: New Kerberos/Certificate tracing options, and multiple new modules

New Tracing Options As hard as we try to ensure that Metasploit is bug free, issues inevitably come up. Whether you’re running a module on an op or writing a new one, what we can do is make the debugging experience easier. To that end one of our two Google Summer of Code (GSoC) projects is here to deliver. Building on the previous pattern of HttpTrace comes two new options KerberosTicketTrace and

Rapid7
MEDIUMVulnerability

Ozempic Drug Maker Loses Clinical Trial Data in Hack

<img src="https://ismg-cdn.nyc3.cdn.digitaloceanspaces.com/articles/ozempic-drug-maker-loses-clinical-trial-data-in-hack-image_small-6-a-31962.jpg" align=right hspace=4><b>Novo Nordisk Breach Involved 'Copying' of Patient, Healthcare Provider Info</b><br>A hack on Danish pharmaceutical manufacturer Novo Nordisk has compromised some patients' clinical trial information, the maker of popular weight

Bank Info Security
MEDIUMVulnerability

ISACA Survey: AI Adoption Is Rising, Visibility Is Not

<img src="https://ismg-cdn.nyc3.cdn.digitaloceanspaces.com/articles/isaca-survey-ai-adoption-rising-visibility-not-image_small-7-a-31960.jpg" align=right hspace=4><b>Governance Professionals Struggle to Measure ROI and Control AI Systems</b><br>AI is becoming embedded across the enterprise, yet many organizations still can't quantify its value or answer key questions about oversight and control. I

Bank Info Security