Skip to main content
VulnerabilityPublished Updated

Wasmtime wasi: WASI filesystem sandbox escape on Windows through a drive-prefixed path component

Affects wasmtime-wasiSource GCVE Database

0

CVSS 7.5 High · fixed in 50.0.3 : patch wasmtime-wasi soon.

Data as of 20 Nov 2026, 13:41 UTC

CVSS 4.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 50.0.3, 49.0.7, 48.0.10 +1
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

What to do

Upgrade wasmtime-wasi to 50.0.3, 49.0.7, 48.0.10 or 36.0.22.

Affected software

ProductAffectedFixed in
crates.iowasmtime-wasipkg:cargo/wasmtime-wasiOther threatsAffected
  • >=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
Fixed in
  • 36.0.22
  • 48.0.10
  • 49.0.7
  • 50.0.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patches by upgrading Wasmtime to versions 36.0.22, 48.0.10, 49.0.7, or 50.0.3 or later. These versions contain fixes that address the filesystem sandbox escape vulnerability. No other mitigation is indicated by the vendor advisory.

Description

A high-severity vulnerability in Wasmtime's WASI implementation allows filesystem sandbox escape on Windows via a drive-prefixed path component. This affects multiple Wasmtime versions prior to fixed releases. The flaw enables an attacker with limited privileges to potentially bypass sandbox restrictions. Official patches are available in Wasmtime versions 36.0.22, 48.0.10, 49.0.7, and 50.0.3.

References

Community reviews

Loading reviews…