CVE-2026-47261
Fixed in a distro release EPSS <1%CVSS 7.5
Wasmtime is a runtime for WebAssembly. In versions prior to 24.0.9, 36.0.10, and 44.0.2, when a filesystem preopen is given DirPerms::all() and FilePerms::READ without FilePerms::WRITE, this access control mechanism can be bypassed via the wasip2 descriptor.open-at or wasip1 path_open interfaces by opening a file with only the OpenFlags::TRUNCATE oflag. The root cause is that the clause handling OpenFlags::TRUNCATE in crates/wasi/src/filesystem.rs (Dir::open_at, lines 967–969) did not set open_mode |= OpenMode::WRITE;, which is later used for the access control check against FilePerms to determine whether opening the file is permitted; the single-line fix adds that missing assignment, after which the affected calls correctly fail with error-code.not-permitted and ERRNO_PERM respectively. Only wasmtime-wasi embeddings that combine DirPerms::MUTATE with FilePerms::READ are affected by this bug. In particular, the Wasmtime project's wasmtime-cli's use of wasmtime-wasi is not affected, because it always sets FilePerms::all() for all preopens. This issue has been fixed in versions 24.0.9, 36.0.10 and44.0.2.
Products: bytecodealliance wasmtime
Fixed upstream
| Ecosystem | Package | Fixed in |
|---|---|---|
| crates.io | wasmtime-wasi | 44.0.2 |
| crates.io | wasmtime-wasi | 36.0.10 |
| crates.io | wasmtime-wasi | 24.0.9 |
| crates.io | wasmtime-wasi | 45.0.0 |
Distro releases
| Release | Package | Fixed in |
|---|---|---|
| Chainguard | wizer | 11.0.3-r12 |
| Chainguard | zed | 1.5.4-r1 |
| Debian 13 | rust-wasmtime | no fix |
| Debian 14 | rust-wasmtime | 36.0.11+dfsg-1 |
| Ubuntu 24.04 LTS | rust-wasmtime | no fix |
| Ubuntu 25.10 | rust-wasmtime | no fix |
| Ubuntu 26.04 LTS | rust-wasmtime | no fix |
| Ubuntu 26.10 | rust-wasmtime | no fix |
| Wolfi | wizer | 11.0.3-r12 |
| Wolfi | zed | 1.5.4-r1 |