Skip to main content
VulnerabilityPublished

CVE-2026-118688: bytecodealliance wasmtime · UNIX Symbolic Link (Symlink) Following

Affects bytecodealliance wasmtimeSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High · fixed in 49.0.3 : patch bytecodealliance wasmtime soon.

Data as of 28 Oct 2026, 19:27 UTC

CVSS 4.0 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 49.0.3, 48.0.6, 36.0.18
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade bytecodealliance wasmtime to 49.0.3, 48.0.6 or 36.0.18.

Affected software

ProductAffectedFixed in
bytecodealliancewasmtimeAffected
  • >=49.0.0 <49.0.3
Fixed in
  • 49.0.3
bytecodealliancewasmtimeAffected
  • >=37.0.0 <48.0.6
Fixed in
  • 48.0.6
bytecodealliancewasmtimeAffected
  • <36.0.18
Fixed in
  • 36.0.18
crates.iowasmtimepkg:cargo/wasmtimeOther threatsAffected
  • <36.0.18
  • >=37.0.0 <48.0.6
  • >=49.0.0 <49.0.3
Fixed in
  • 36.0.18
  • 48.0.6
  • 49.0.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

This vulnerability is fixed in Wasmtime versions 36.0.18, 48.0.6, and 49.0.3. Users should upgrade to these or later versions to remediate the issue. No additional mitigation steps are indicated in the advisory.

Description

CVE-2026-118688 is a vulnerability in wasmtime-wasi in Wasmtime versions before 36.0.18, 48.0.6, and 49.0.3. It involves the re-appending of a trailing slash to rename source paths, which causes the renameat system call on macOS and FreeBSD hosts to follow directory symbolic links (symlinks). This allows a guest with sandbox write access to rename a relative symlink such as "up/" to move host directories into its sandbox, potentially enabling unauthorized read or write access to host directories.

References

Community reviews

Loading reviews…