Advisory

GHSA-6wgr-89rj-399p

Also known as: CVE-2026-34988, RUSTSEC-2026-0088

Summary

Wasmtime has data leakage between pooling allocator instances

Details

Impact

Wasmtime's implementation of its pooling allocator contains a bug where in certain configurations the contents of linear memory can be leaked from one instance to the next. The implementation of resetting the virtual memory permissions for linear memory used the wrong predicate to determine if resetting was necessary, where the compilation process used a different predicate. This divergence meant that the pooling allocator incorrectly deduced at runtime that resetting virtual memory permissions was not necessary while compile-time determine that virtual memory could be relied upon.

Exposing this bug requires specific configuration values to be used. If any of these configurations are not applicable then this bug does not happen:

  • The pooling allocator must be in use.
  • The Config::memory_guard_size configuration option must be 0.
  • The Config::memory_reservation configuration must be less than 4GiB.
  • The pooling allocator must be configured with max_memory_size the same as the memory_reservation value.

If all of these conditions are applicable then when a linear memory is reused the VM permissions of the previous iteration are not reset. This means that the compiled code, which is assuming out-of-bounds loads will segfault, will not actually segfault and can read the previous contents of linear memory if it was previously mapped.

This represents a data leakage vulnerability between guest WebAssembly instances which breaks WebAssembly's semantics and additionally breaks the sandbox that Wasmtime provides. Wasmtime is not vulnerable to this issue with its default settings, nor with the default settings of the pooling allocator, but embeddings are still allowed to configure these values to cause this vulnerability.

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

All four conditions above must be met to be vulnerable to this bug, and users can work around this bug by adjusting any of the above conditions. For example it is strongly recommended that guard pages are configured for linear memories which would make this bug not applicable.

Severity

Low Basis: The source's own band: LOW

Dates

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

Affected packages and fixes

wasmtime

crates.io · All systems

Affected

  • introduced 28.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