cve.bz

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

8.8 highEPSS 0.2%Fix available

High (8.8) in bytecodealliance wasmtime. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in wasmtime-wasi 36.0.18, 48.0.6, 49.0.3.

On this page
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.

Severity

CVSS 4.0

8.8 high
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

CVSS 3.1

7.9 high
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:L
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-61 UNIX Symbolic Link (Symlink) Following
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-118688 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118688?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118688?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-118688 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
bytecodealliance wasmtimebefore 36.0.18
bytecodealliance wasmtimefrom 37.0.0 before 48.0.6
bytecodealliance wasmtimefrom 49.0.0 before 49.0.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
RUSTSEC-2026-0352crates.iowasmtime-wasi>=0.0.0-0 <36.0.18
>=37.0.0 <48.0.6
>=49.0.0 <49.0.3
36.0.18, 48.0.6, 49.0.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13rust-wasmtimeno fix listedDEBIAN-CVE-2026-118688
Debian14rust-wasmtime36.0.20+dfsg-1DEBIAN-CVE-2026-118688

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON