Advisory

GHSA-m9w2-8782-2946

Also known as: CVE-2026-34945, RUSTSEC-2026-0086

Summary

Wasmtime has host data leakage with 64-bit tables and Winch

Details

Impact

Wasmtime's Winch compiler contains a bug where a 64-bit table, part of the memory64 proposal of WebAssembly, incorrectly translated the table.size instruction. This bug could lead to disclosing data on the host's stack to WebAssembly guests. The host's stack can possibly contain sensitive data related to other host-originating operations which is not intended to be disclosed to guests.

This bug specifically arose from a mistake where the return value of table.size was statically typed as a 32-bit integer, as opposed to consulting the table's index type to see how large the returned register could be. When combined with details about Wnich's ABI, such as multi-value returns, this can be combined to read stack data from the host, within a guest. This information disclosure should not be possible in WebAssembly, violates spec semantics, and is a vulnerability in Wasmtime.

Patches

Wasmtime 36.0.7, 42.0.2, and 43.0.1 have been issued to fix this bug. Users are recommended to update to these patched versions of Wasmtime.

Workarounds

Users of Cranelift are not affected by this issue, but users of Winch have no workarounds other than disabling the Config::wasm_memory64 proposal.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2026-04-09 20:23 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

wasmtime

crates.io · All systems

Affected

  • introduced 25.0.0, fixed 36.0.7 (semver)

Fixed versions

36.0.7

Fix

  • Fixed version 36.0.7
    cargo update -p wasmtime --precise 36.0.7

wasmtime

crates.io · All systems

Affected

  • introduced 37.0.0, fixed 42.0.2 (semver)

Fixed versions

42.0.2

Fix

  • Fixed version 42.0.2
    cargo update -p wasmtime --precise 42.0.2

wasmtime

crates.io · All systems

Affected

  • introduced 43.0.0, fixed 43.0.1 (semver)

Fixed versions

43.0.1

Fix

  • Fixed version 43.0.1
    cargo update -p wasmtime --precise 43.0.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences