Filesystem sandbox escape when renaming symlinks with trailing slashes
CVE-2026-118688GHSA-m9f7-9w4p-gv38
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (wasmtime-wasi 49.0.3, 48.0.6, 36.0.18), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
crates.io wasmtime-wasi
- Affected
- >= 0.0.0-0, < 36.0.18>= 37.0.0, < 48.0.6>= 49.0.0, < 49.0.3
- Fixed in
- 48.0.6, 49.0.3, 36.0.18
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record RUSTSEC-2026-0352 lists affected ranges: crates.io wasmtime-wasi >=0.0.0-0 =37.0.0 =49.0.0 <49.0.3 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 8.8 · 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 · score source
- EPSS
- CVE-2026-118688: 0.24% estimated exploitation activity in the next 30 days; percentile 15.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
This is an entry in the RustSec database for the Wasmtime security advisory located at https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-m9f7-9w4p-gv38 For more information see the GitHub-hosted security advisory.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from osv record RUSTSEC-2026-0352
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record RUSTSEC-2026-0352
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-118688 Advisory: Filesystem sandbox escape when renaming symlinks with trailing slashes IDs: CVE-2026-118688, GHSA-m9f7-9w4p-gv38 Record: https://patchnext.com/advisories/rustsec-2026-0352 (revision 3, source checked 30 Oct 2026, 07:10 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 8.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: wasmtime-wasi 49.0.3, 48.0.6, 36.0.18. A vendor fix does not mean a deployment is fixed. ## Affected components - crates.io wasmtime-wasi: affected >= 0.0.0-0, < 36.0.18; >= 37.0.0, < 48.0.6; >= 49.0.0, < 49.0.3; fixed in 48.0.6, 49.0.3, 36.0.18 ## Suggested inspection (read-only) - crates.io wasmtime-wasi: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on wasmtime-wasi. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0352 (OSV record RUSTSEC-2026-0352 lists affected ranges: crates.io wasmtime-wasi >=0.0.0-0 =37.0.0 =49.0.0 <49.0.3 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…