Bug 2456994 (CVE-2026-35195) - CVE-2026-35195 Wasmtime: Wasmtime: Data corruption and potential arbitrary code execution via unvalidated memory reallocation
Summary: CVE-2026-35195 Wasmtime: Wasmtime: Data corruption and potential arbitrary co...
Keywords:
Status: NEW
Alias: CVE-2026-35195
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 2457171
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-09 19:01 UTC by OSIDB Bzimport
Modified: 2026-04-09 22:52 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-04-09 19:01:38 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.