Advisory

GHSA-hx6p-xpx3-jvvv

Also known as: CVE-2026-34941, RUSTSEC-2026-0093

Summary

Wasmtime: Heap OOB read in component model UTF-16 to latin1+utf16 string transcoding

Details

Summary

Wasmtime contains a vulnerability where when transcoding a UTF-16 string to the latin1+utf16 component-model encoding it would incorrectly validate the byte length of the input string when performing a bounds check. Specifically the number of code units were checked instead of the byte length, which is twice the size of the code units.

This vulnerability can cause the host to read beyond the end of a WebAssembly's linear memory in an attempt to transcode nonexistent bytes. In Wasmtime's default configuration this will read unmapped memory on a guard page, terminating the process with a segfault. Wasmtime can be configured, however, without guard pages which would mean that host memory beyond the end of linear memory may be read and interpreted as UTF-16.

A host segfault is a denial-of-service vulnerability in Wasmtime, and possibly being able to read beyond the end of linear memory is additionally a vulnerability. Note that reading beyond the end of linear memory requires nonstandard configuration of Wasmtime, specifically with guard pages disabled.

Impact

This is an out-of-bounds memory access. Any user running untrusted wasm components that use cross-component string passing (with UTF-16 source and latin1+utf16 destination encodings) is affected.

  • With guard pages: Denial of service. The host process crashes with SIGBUS/SIGSEGV.
  • Without guard pages: Potential information disclosure. The guest can read host memory beyond its linear memory allocation.

Patches

Wasmtime 24.0.7, 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

There is no workaround for this bug. Hosts are recommended to updated to a patched version of Wasmtime.

Severity

Medium Basis: The source's own band: MODERATE

Dates

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

Affected packages and fixes

wasmtime

crates.io · All systems

Affected

  • introduced 0, fixed 24.0.7 (semver)

Fixed versions

24.0.7

Fix

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

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