Rust advisories / crate
Security history · wasmtime-wasi · data from Oct 24, 2026
Is wasmtime-wasi safe to use? Its security history
VerdictNo open advisories. 9 past vulnerabilities were fixed; use 49.0.3 or newer to be clear of all of them.
9advisories on record
9vulnerabilities
0unmaintained notices
49.0.3newest fixed version
Every advisory, newest first
- VulnerabilityRUSTSEC-2026-0352 · 2026-10-14Filesystem sandbox escape when renaming symlinks with trailing slashes
- Vulnerability MediumRUSTSEC-2026-0321 · 2026-10-02WASI preview 0 implementation of `poll_oneoff` circumvents fuel consumption
- VulnerabilityRUSTSEC-2026-0322 · 2026-10-02Excessive allocated memory on the host when guests don't have stdio
- VulnerabilityRUSTSEC-2026-0323 · 2026-10-02fd_readdir copies uninitialized struct padding into guest memory
- Vulnerability MediumRUSTSEC-2026-0324 · 2026-10-02Guest can panic host through filesystem timestamp before the epoch on wasip3
- Vulnerability MediumRUSTSEC-2026-0314 · 2026-09-24Guest can panic host through filesystem datetime overflow
- Vulnerability MediumRUSTSEC-2026-0188 · 2026-06-24WASI hard links and renames bypass wasmtime-wasi's FilePerms for destination
- VulnerabilityRUSTSEC-2026-0182 · 2026-06-15Leak in WASIp1 `fd_renumber` implementation
- Vulnerability HighRUSTSEC-2026-0149 · 2026-05-21WASI path_open(TRUNCATE) bypasses `FilePerms::WRITE` host restriction
Check your version
Run cargo tree -i wasmtime-wasi to see which version you build and why, or paste your Cargo.lock into the Cargo.toml checker to match every advisory against your exact versions.
RustSec advisories (CC0-1.0) and GitHub-reviewed advisories via OSV's crates.io export, downloaded Oct 24, 2026.
Up next
Are you affected?Check your whole dependency treeRead it next →Also worth your time
Did this answer your question?