CVE-2026-47261

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

HIGH
7.5
CVSS Score
Published: June 15, 2026 at 07:47 PM UTC
Updated: October 25, 2026 at 11:10 PM UTC
1 product affected across 1 vendorWasmtime

Using wasmtime by bytecodealliance?

Get instant alerts when new vulnerabilities affect wasmtime - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.4%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 24.0.925.0.0 ≤ v < 36.0.1037.0.0 ≤ v < 44.0.2
Affected range stops below 24.0.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 36.0.10, so it looks safe — our inference, not a vendor statement
Affected range stops below 44.0.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (5)

x_refsource_CONFIRMMitigationVendor Advisory
Source: cverecord
https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-2r75-cxrj-cmph
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/bytecodealliance/wasmtime/releases/tag/v24.0.9
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/bytecodealliance/wasmtime/releases/tag/v36.0.10
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/bytecodealliance/wasmtime/releases/tag/v44.0.2
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/bytecodealliance/wasmtime/releases/tag/v45.0.0

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-284NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card