Bytecodealliance · product
wasmtime
86 CVEs
Every dot is a CVE in what this vendor ships; the named ones are the most at risk.
Every one of the 86 is a mark on the map. Named now: 1 to 26, most at risk first.
- Miscompilation of `i8x16.swizzle` and `select` with v128 inputs in Wasmtime
- Guest-controlled out-of-bounds read/write on x86_64 in wasmtime
- Use After Free in Wasmtime
- Use after free in Wasmtime
- Wasmtime: Cranelift backend on aarch64 can jump to incorrect target on large Wasm `br_table` instruction
- Wasmtime vulnerable to data leakage between instances in the pooling allocator
- Cranelift vulnerable to miscompilation of constant values in division on AArch64
- Wasmtime doesn't fully sandbox all the Windows device filenames
- Wasmtime vulnerable to out of bounds read/write with zero-memory-pages configuration
- Invalid drop of partially-initialized instances in wasmtime
- Miscompilation of wasm `i64x2.shr_s` instruction with constant input on x86_64
- wasmtime is a fast and secure runtime for WebAssembly. Wasmtime's code generation backend, Cranelift, has a bug on x86_64 platforms for the WebAssembly `i8x16.select` instruction…
- Wasmtime can panic when adding excessive fields to a `wasi:http/types.fields` instance
- Memory access due to code generation flaw in Cranelift module
- Wasmtime: Bit-packing in Cranelift compiler causes silent overflow and miscompilation
- Wasmtime has Undefined Behavior in Rust runtime functions
- Wasmtime: Panic lowering a host-created component model stream into a guest that expects a different payload type
- wasmtime_trap_code C API function has out of bounds write vulnerability
- Wasmtime vulnerable to segfault when using component resources
- Wasmtime is vulnerable to panic when dropping a `[Typed]Func::call_async` future
- Wasmtime WASI implementations are vulnerable to guest-controlled resource exhaustion
- Wasmtime 42.0.0 before 48.0.6 and 49.0.0 before 49.0.3 Stack Overflow via Type Registry
- Wasmtime has a Heap OOB read in component model UTF-16 to latin1+utf16 string transcoding
- Wasmtime has host panic with `fd_renumber` WASIp1 function
- Wasmtime's host panics when Winch compiler executes `table.fill`
- Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 Host Panic via realloc
exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it
Zoom in on the map and the dots under the middle of it are named where they are.
Data as of 2026-11-15. CVE List through 2026-11-15 · EPSS of 2026-11-14 · CISA KEV checked 2026-11-15. Sources: the CVE List, CISA KEV, EPSS, NVD, nuclei templates and public bug bounty data.