Live › vulnerability › CVE-2026-118688
Go to dashboardWasmtime's wasi rename path handling re-appends a trailing slash, so renameat follows directory symlinks on macOS and FreeBSD hosts. A guest with write access to its sandbox can move host directories into it and read or write them.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 19:34 UTC. All times on this page are UTC.
Applications that embed Wasmtime and give untrusted guest code preopened directories with write access, running on macOS or FreeBSD hosts. Sandboxes that run only trusted code, or have no writable preopened directories, have less exposure. Linux hosts are not described as affected.
No product ranges from the sources yet.
wasmtime --version or the wasmtime-wasi crate version in Cargo.lock36.0.18, 48.0.6, or 49.0.3 depending on release lineEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
wasmtime-wasi in Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 re-appends a trailing slash to rename source paths, causing renameat on macOS and FreeBSD hosts to follow directory symlinks. A guest with sandbox write access can rename a relative symlink such as "up/" to move host directories into its sandbox and read or write them.
This page as .md · .json · in your agent: get_signal("CVE-2026-118688")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.