# CVE-2026-115392: Wasmtime before 24.0.13, 25.0.0 before 36.0.14, 37.0.0 before 46.0.3, and 47.0.0 before 47.0.4 allows a filesystem sandbox escape in wasmtim


- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** AZL-111068, DEBIAN-CVE-2026-115392, GHSA-gxhv-gf3j-vwqc, GHSA-vqjp-4c8c-hfgg, RUSTSEC-2026-0269, UBUNTU-CVE-2026-115392

## What is CVE-2026-115392?

CVE-2026-115392 is a high-severity vulnerability in bytecodealliance wasmtime, published on 22 Oct 2026. 

### Official description

Wasmtime before 24.0.13, 25.0.0 before 36.0.14, 37.0.0 before 46.0.3, and 47.0.0 before 47.0.4 allows a filesystem sandbox escape in wasmtime-wasi because its cap-std dependency mishandles symlinks with trailing slashes on macOS and Linux kernels lacking openat2. A guest with write access to any sandboxed directory can read and write any host-accessible file, and read-only guests may read host files via preexisting symlinks.

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following)

## Which versions are affected by CVE-2026-115392?

1 open source package ship an affected version, including wasmtime.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wasmtime` | crates.io | From 0.0.0-0 | 24.0.13, 36.0.14, 46.0.3, 47.0.4 |

## How do I fix CVE-2026-115392?

Upgrade wasmtime to a fixed version for your release line: 24.0.13, 36.0.14, 46.0.3 or 47.0.4.

## Is CVE-2026-115392 being exploited?

There is no known exploitation of CVE-2026-115392 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115392 and fix it if it is affected.

What it is: CVE-2026-115392 is a high-severity vulnerability in bytecodealliance wasmtime, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115392 in the wild and no public exploit code.

Affected packages and fixed versions:
- wasmtime (crates.io): affected from 0.0.0-0; fixed in 24.0.13, 36.0.14, 46.0.3, 47.0.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-115392/ (Markdown: https://insights.sbomify.com/CVE-2026-115392/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-115392
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-115392
- OSV: https://osv.dev/vulnerability/CVE-2026-115392

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-115392/
Summaries are generated and may contain mistakes; the official description above is the record.