RUSTSEC-2026-0587: WASI filesystem sandbox escape on Windows through a drive-prefixed path component

Unknown

OSV id
RUSTSEC-2026-0587
Also known as
GHSA-f2pq-268w-886c
Published
Last modified

Affected packages

PackageAffected versionsFixed in
wasmtime-wasi
Cargo
>= 0.0.0-0, < 36.0.22
>= 37.0.0, < 48.0.10
>= 49.0.0, < 49.0.7
>= 50.0.0, < 50.0.3
36.0.22, 48.0.10, 49.0.7, 50.0.3

How to fix it

Upgrade wasmtime-wasi to the fixed version of the release line you use (36.0.22, 48.0.10, 49.0.7, 50.0.3), or to 50.0.3 or later.

cargo update -p wasmtime-wasi --precise 50.0.3
  • If it is an indirect dependency, `cargo update -p` still works; if a parent crate pins an older version, upgrade that crate.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-f2pq-268w-886c For more information see the GitHub-hosted security advisory.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: RustSec Advisory Database via OSV.dev (CC0 1.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.