wasmtime
Affected
- introduced
30.0.0, fixed36.0.8(semver)
Fixed versions
36.0.8
Fix
- Fixed version
36.0.8cargo update -p wasmtime --precise 36.0.8
Advisory
Also known as: CVE-2026-44216, RUSTSEC-2026-0114
wasmtime has a panic when allocating a table exceeding the size of the host's address space
Impact
Wasmtime's allocation logic for a WebAssembly table contained checked arithmetic which panicked on overflow. This overflow is possible to trigger, and thus panic, when a table with an extremely large size is allocated. This is possible with the WebAssembly memory64 proposal where tables can have sizes in the 64-bit range as opposed to the previous 32-bit range which would not overflow. The panic happens when attempting to create a very large table, such as when instantiating a WebAssembly module or component.
This bug does not affect the pooling allocator which limits tables sizes to much less than the required amount to trigger the overflow. This bug is only present for the on-demand instance allocator, which is Wasmtime's default allocator. This bug also requires the memory64 WebAssembly feature to be enabled, which is on-by-default.
Panicking in the host process is considered a denial-of-service vector for Wasmtime.
Patches
Wasmtime 36.0.8, 43.0.2, and 44.0.1 have all been released which fixes this issue.
Workarounds
Embeddings can switch to using the pooling allocator to work around this issue, or the memory64 WebAssembly proposal can be disabled. Otherwise there is no workaround and users are recommended to upgrade.
Medium Basis: The source's own band: MODERATE
30.0.0, fixed 36.0.8 (semver)36.0.8
36.0.8cargo update -p wasmtime --precise 36.0.837.0.0, fixed 43.0.2 (semver)43.0.2
43.0.2cargo update -p wasmtime --precise 43.0.2Fix 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
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0