Skip to content
Log inStart free trial

RUSTSEC-2026-0149 CVE-2026-47261 GHSA-2r75-cxrj-cmph

WASI path_open(TRUNCATE) bypasses `FilePerms::WRITE` host restriction

High crates.io
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.36%
Chance of exploitation in the next 30 days. Higher than 29.48% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
44.0.2
Upgrade wasmtime-wasi to this version or later

Description

This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-2r75-cxrj-cmph For more information see the GitHub-hosted security advisory.

Affected versions

crates.io

PackageVulnerableFixed in
wasmtime-wasi
>= 37.0.0, < 44.0.2
44.0.2
wasmtime-wasi
>= 25.0.0, < 36.0.10
36.0.10
wasmtime-wasi
< 24.0.9
24.0.9
wasmtime-wasi
>= 0.0.0-0, < 24.0.9
>= 25.0.0, < 36.0.10
>= 37.0.0, < 44.0.2
>= 45.0.0, < 45.0.0
24.0.9
36.0.10
44.0.2
45.0.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

wasmtime-wasi crates.io → 44.0.2

cargo
cargo update -p wasmtime-wasi --precise 44.0.2

Severity breakdown

CVSS 3.1 7.5

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Advisories

Packages

Other links

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
RUSTSEC-2026-0420
wasip3 UDP `send` can deliver a datagram to an address only allowed for receiving
Medium Also affects wasmtime-wasi
RUSTSEC-2026-0352
Filesystem sandbox escape when renaming symlinks with trailing slashes
Not rated yet Also affects wasmtime-wasi
RUSTSEC-2026-0324
Guest can panic host through filesystem timestamp before the epoch on wasip3
Medium Also affects wasmtime-wasi
RUSTSEC-2026-0321
WASI preview 0 implementation of `poll_oneoff` circumvents fuel consumption
Medium Also affects wasmtime-wasi
RUSTSEC-2026-0323
fd_readdir copies uninitialized struct padding into guest memory
Low Also affects wasmtime-wasi
RUSTSEC-2026-0322
Excessive allocated memory on the host when guests don't have stdio
Medium Also affects wasmtime-wasi
RUSTSEC-2026-0314
Guest can panic host through filesystem datetime overflow
Medium Also affects wasmtime-wasi
GHSA-4ch3-9j33-3pmj
Wasmtime: WASI hard links bypass wasmtime-wasi's FilePerms for destination
Medium Also affects wasmtime-wasi
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor