Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| bytecodealliance | wasmtime | >= 25.0.0, < 36.0.7 | - |
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-35195 | Wasmtime has an out-of-bounds write or crash when transcoding component model strings | |
| CVE-2026-35186 | Wasmtime has an improperly masked return value from `table.grow` with Winch compiler backe | |
| CVE-2026-34983 | Wasmtime has a use-after-free bug after cloning `wasmtime::Linker` | |
| CVE-2026-34941 | Wasmtime has a Heap OOB read in component model UTF-16 to latin1+utf16 string transcoding | |
| CVE-2026-34942 | Wasmtime panics when transcoding misaligned utf-16 strings | |
| CVE-2026-34988 | Wasmtime leaks data between pooling allocator instances | |
| CVE-2026-34971 | Wasmtime miscompiled guest heap access enables sandbox escape on aarch64 Cranelift | |
| CVE-2026-34946 | Wasmtime's host panics when Winch compiler executes `table.fill` | |
| CVE-2026-34944 | Wasmtime segfault or unused out-of-sandbox load with `f64x2.splat` operator on x86-64 | |
| CVE-2026-34945 | Wasmtime leaks host data with 64-bit tables and Winch | |
| CVE-2026-34943 | Wasmtime panics when lifting `flags` component value |
No comments yet