Bug 2496796 - CVE-2026-47261 tree-sitter: Wasmtime: Access control bypass allows unauthorized file truncation via specific open flags. [fedora-all]
Summary: CVE-2026-47261 tree-sitter: Wasmtime: Access control bypass allows unauthoriz...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: tree-sitter
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Andreas Schneider
QA Contact:
URL:
Whiteboard: {"flaws": ["3cc8d107-2fd3-40e5-8850-2...
Depends On:
Blocks: CVE-2026-47261
TreeView+ depends on / blocked
 
Reported: 2026-07-03 09:08 UTC by Ganesh
Modified: 2026-07-03 09:08 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ganesh 2026-07-03 09:08:34 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

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.


Note You need to log in before you can comment on or make changes to this bug.