CVE-2026-44216: 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.
Published May 7, 2026 · Updated May 14, 2026
Affected packages
wasmtime
- Ecosystem
- Rust (crates.io)
- Affected
- >= 30.0.0, < 36.0.8
- Fixed in
- 36.0.8
- Check
cargo tree -i wasmtime
wasmtime
- Ecosystem
- Rust (crates.io)
- Affected
- >= 37.0.0, < 43.0.2
- Fixed in
- 43.0.2
- Check
cargo tree -i wasmtime
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Rust (crates.io) vulnerabilities
All Rust (crates.io) entriesCVE-2026-115893
Wasmtime: Cranelift backend on aarch64 can jump to incorrect target on large Wasm `br_table` instruction
critical9.9Oct 28, 2026CVE-2026-115889
Wasmtime: Bit-packing in Cranelift compiler causes silent overflow and miscompilation
critical9.9Oct 23, 2026CVE-2026-115892
Wasmtime: Panic lowering a host-created component model stream into a guest that expects a different payload type
medium5.7Oct 23, 2026CVE-2026-104855
Wasmtime: Preemption and traps during bulk operations enable breaking internal VM state
low2.0Oct 2, 2026CVE-2026-34987
Wasmtime with Winch compiler backend on aarch64 may allow a sandbox-escaping memory access
critical9.2Apr 10, 2026CVE-2026-35186
Wasmtime has improperly masked return value from `table.grow` with Winch compiler backend
medium6.1Apr 10, 2026
