Advisory

GHSA-2r75-cxrj-cmph

Also known as: CVE-2026-47261, RUSTSEC-2026-0149

Summary

wasmtime-wasi: WASI path_open(TRUNCATE) bypasses FilePerms::WRITE host restriction

Details

Summary

In wasmtime-wasi, when a filesystem preopen is given DirPerms::all() and FilePerms::READ without FilePerms::WRITE, this wasmtime-wasi enforced access control mechanism can be bypassed by using the wasip2 descriptor.open-at or wasip1 path_open interfaces by opening a file with OpenFlags::TRUNCATE oflag only, for example:

dir_descriptor.open_at(
   PathFlags::empty(),
   FILENAME,
   OpenFlags::TRUNCATE,
   DescriptorFlags::READ,
)
wasip1::path_open(
    dir_fd,
    0,
    FILENAME,
    wasip1::OFLAGS_TRUNC,
    wasip1::RIGHTS_FD_READ,
    0,
    0
)

The root cause is that the clause that considered OpenFlags::TRUNCATE did not set open_mode |= OpenMode::WRITE;, used later in that function for the access control check against FilePerms for whether opening that file is permitted. With the bug corrected, these calls to open-at and path_open fail with error-code.not-permitted and ERRNO_PERM respectively.

The bug in crates/wasi/src/filesystem.rs, Dir::open_at, lines 967–969:

if oflags.contains(OpenFlags::TRUNCATE) {
    opts.truncate(true).write(true);
}

and the single line fix is:

if oflags.contains(OpenFlags::TRUNCATE) {
    opts.truncate(true).write(true);
    open_mode |= OpenMode::WRITE;
}

Only wasmtime-wasi embeddings that use a combination of DirPerms::MUTATE with FilePerms::READ are affected by this bug, e.g. those that use in the WasiCtxBuilder:

builder.preopened_dir("readonly", "readonly", DirPerms::READ | DirPerms::MUTATE, FilePerms::READ);

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.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2026-06-05 15:47 UTC
Modified
2026-09-10 03:51 UTC

Affected packages and fixes

wasmtime-wasi

crates.io · All systems

Affected

  • introduced 37.0.0, fixed 44.0.2 (semver)

Fixed versions

44.0.2

Fix

  • Fixed version 44.0.2
    cargo update -p wasmtime-wasi --precise 44.0.2

wasmtime-wasi

crates.io · All systems

Affected

  • introduced 25.0.0, fixed 36.0.10 (semver)

Fixed versions

36.0.10

Fix

  • Fixed version 36.0.10
    cargo update -p wasmtime-wasi --precise 36.0.10

wasmtime-wasi

crates.io · All systems

Affected

  • introduced 0, fixed 24.0.9 (semver)

Fixed versions

24.0.9

Fix

  • Fixed version 24.0.9
    cargo update -p wasmtime-wasi --precise 24.0.9

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences