CVE-2026-34971 json
Wasmtime miscompiled guest heap access enables sandbox escape on aarch64 Cranelift
published 2026-04-09 7 mo ago modified 2026-10-26 13 d ago also EUVD-2026-21027 , GHSA-jhxm-h53p-jm7w , JLSEC-2026-1360 , RUSTSEC-2026-0096
- cvss
- 8.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 25%
- public exploits
- 0
- none known
Summary
Wasmtime is a runtime for WebAssembly. From 32.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime's Cranelift compilation backend contains a bug on aarch64 when performing a certain shape of heap accesses which means that the wrong address is accessed. When combined with explicit bounds checks a guest WebAssembly module this can create a situation where there are two diverging computations for the same address: one for the address to bounds-check and one for the address to load. This difference in address being operated on means that a guest module can pass a bounds check but then load a different address. Combined together this enables an arbitrary read/write primitive for guest WebAssembly when accesssing host memory. This is a sandbox escape as guests are able to read/write arbitrary host memory. This vulnerability has a few ingredients, all of which must be met, for this situation to occur and bypass the sandbox restrictions. This miscompiled shape of load only occurs on 64-bit WebAssembly linear memories, or when Config::wasm_memory64 is enabled. 32-bit WebAssembly is not affected. Spectre mitigations or signals-based-traps must be disabled. When spectre mitigations are enabled then the offending shape of load is not generated. When signals-based-traps are disabled then spectre mitigations are also automatically disabled. The specific bug in Cranelift is a miscompile of a load of the shape load(iadd(base, ishl(index, amt))) where amt is a constant. The amt value is masked incorrectly to test if it's a certain value, and this incorrect mask means that Cranelift can pattern-match this lowering rule during instruction selection erroneously, diverging from WebAssembly's and Cranelift's semantics. This incorrect lowering would, for example, load an address much further away than intended as the correct address's computation would have wrapped around to a smaller value insetad. This vulnerability is fixed in 36.0.7, 42.0.2, and 43.0.1.
Patch / fix
- crates.io wasmtime 36.0.7, 42.0.2, 43.0.1
- julia Wasmtime_jll 45.0.1+0
- bytecodealliance wasmtime 36.0.7, 42.0.2, 44.0.1
- rust-wasmtime Debian 14 36.0.7+dfsg-1
debian advisories DEBIAN-CVE-2026-34971
- github.com/bytecodealliance/wasmtime#13013 pull request
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-34971 updated cvss 8.5
wasmtime: cranelift: Wasmtime: Sandbox escape due to miscompiled heap access on aarch64
-
Red Hat Connectivity Link 1 redhat-user-workloads/api-management-tenant/rhcl-1-3-wasm-shimaffected: workaround, no fix available
-
Red Hat Enterprise Linux 10 virt-firmware-rsnot affected: component not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 6 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 25% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 9.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 |
| CISA ADP | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
| CISA ADP | 3.1 | 8.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
| CNA | 4.0 | 9.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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
| CNA | 3.1 | 8.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
| OSV | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | wasmtime | >=32.0.0, <36.0.7 >=37.0.0, <42.0.2 >=43.0.0, <43.0.1 >=0.0.0-0, <36.0.7 |
36.0.7 42.0.2 43.0.1 |
| julia | Wasmtime_jll | >=39.0.0+0, <45.0.1+0 |
45.0.1+0 |
Affected products
- bytecodealliance wasmtime
- Red Hat Red Hat Connectivity Link 1
- Red Hat Red Hat Enterprise Linux 10
Classification
References
-
github.com
/bytecodealliance/wasmtime/pull/13013
web
-
github.com
/bytecodealliance/wasmtime/security/advisories/GHSA-jhxm-h53p-jm7w
web, mitigation, vendor-advisory
-
access.redhat.com
/security/cve/CVE-2026-34971
vdb-entry, web
-
bugzilla.redhat.com
/show_bug.cgi?id=2457008
issue-tracking, web
-
security.access.redhat.com
/data/csaf/v2/vex/2026/cve-2026-34971.json
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-34971
advisory, web
-
github.com
/bytecodealliance/wasmtime
package
-
rustsec.org
/advisories/RUSTSEC-2026-0096.html
web, advisory
-
github.com
/advisories/GHSA-jhxm-h53p-jm7w
web
-
crates.io
/crates/wasmtime
package
Sources
- CVE List CVE-2026-34971
- GitHub Advisory GHSA-jhxm-h53p-jm7w
- NVD CVE-2026-34971
- OSV JLSEC-2026-1360
- OSV RUSTSEC-2026-0096
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.