CVE-2026-118688

Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 Sandbox Escape via Symlink Rename

Published Oct 28, 2026 CVSS 4.0 · 8.8 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability re‑appends a trailing slash to rename source paths, causing the macOS and FreeBSD renameat system call to follow directory symlinks. A WASI guest with sandbox write permissions can rename a relative symlink such as "up/" so that host directories are moved into the sandbox, providing the guest read or write access to files outside its intended boundary. This flaw therefore allows an attacker to escape the sandbox and compromise the confidentiality, integrity, or availability of host data.

Affected Systems

Wasmtime before 36.0.18, before 37.0.0 – 48.0.6, and before 49.0.0 – 49.0.3 when running on macOS or FreeBSD hosts. The affected vendor is Bytecode Alliance’s Wasmtime. The vulnerable releases include any version up to 36.0.17, any 37.x and 48.x release prior to 48.0.6, and any 49.x release prior to 49.0.3.

Risk and Exploitability

The CVSS score of 8.8 indicates a high severity. No EPSS score is available, so the exploitation probability cannot be quantified from that metric, and the vulnerability is not listed in CISA KEV. Exploitability requires only a WASI guest with write access in its sandbox; no external network access or system privilege escalation is needed. The flaw arises from improper path handling (CWE‑61), making renaming a relative symlink a powerful technique for gaining unauthorized access to host files.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a Wasmtime upgrade to 36.0.18 or newer, or to 48.0.6 or newer, or to 49.0.3 or newer, to receive the remediation for the symlink rename issue.
  • If an immediate upgrade cannot be performed, deny the sandbox the ability to perform the renameat system call or otherwise restrict write permissions for the WASI guest so that it cannot rename symlinks.
  • Run Wasmtime inside an OS‑level container or chroot environment that limits directory traversal and disables symlink resolution for sensitive paths, thereby reducing the impact even if a sandbox escape occurs.

Generated by OpenCVE AI on October 28, 2026 at 20:45 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Wasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 Sandbox Escape via Symlink Rename
First Time appeared Bytecodealliance
Bytecodealliance wasmtime
Weaknesses CWE-61
CPEs cpe:2.3:a:bytecodealliance:wasmtime:*:*:*:*:*:*:*:*
Vendors & Products Bytecodealliance
Bytecodealliance wasmtime
References
Metrics cvssV3_1

{'score': 7.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:L'}

cvssV4_0

{'score': 8.8, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L'}

Weaknesses
  • CWE-61

    UNIX Symbolic Link (Symlink) Following

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 4, 2026, 3:08 PM
Reserved
Oct 28, 2026, 5:31 PM
Status
Deferred
Published
Oct 28, 2026, 7:17 PM
Modified
Nov 4, 2026, 3:17 PM