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 Sandbox Escape via Trailing Slashes
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No special conditions are required; it is repeatable.
- Fixed version: bytecodealliance wasmtime 24.0.13, 36.0.14, 46.0.3; azl3 rpm-ostree 2024.4-11 on Azure Linux 3.0 Release Notes.
Low priority for now. Upgrade to bytecodealliance wasmtime 24.0.13, 36.0.14, 46.0.3; azl3 rpm-ostree 2024.4-11 on Azure Linux 3.0 Release Notes or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 22, 2026
- Updated
- Oct 29, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-61
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
bytecodealliance wasmtime
- 24.0.13, 36.0.14, 46.0.3, 47.0.4not affected
- before 24.0.13affected · semver
- 25.0.0 and later · before 36.0.14affected · semver
- 37.0.0 and later · before 46.0.3affected · semver
- 47.0.0 and later · before 47.0.4affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| crates.io | wasmtime | from 0.0.0-0 · before 24.0.13 | 24.0.13 |
| crates.io | wasmtime | from 25.0.0 · before 36.0.14 | 36.0.14 |
| crates.io | wasmtime | from 37.0.0 · before 46.0.3 | 46.0.3 |
| crates.io | wasmtime | from 47.0.0 · before 47.0.4 | 47.0.4 |
| Debian:13 | rust-wasmtime | from 0 | — |
| Debian:14 | rust-wasmtime | before 36.0.20+dfsg-1 | 36.0.20+dfsg-1 |
Same product
bytecodealliance: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-115893Wasmtime: Cranelift backend on aarch64 can jump to incorrect target on large Wasm `br_table` instruction39Monitor
- CVE-2026-115889Wasmtime: Bit-packing in Cranelift compiler causes silent overflow and miscompilation39Monitor
- CVE-2022-39394wasmtime_trap_code C API function has out of bounds write vulnerability39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-115390Oct 22, 2026 · Wasmtime 47.0.0 before 48.0.3 and 49.0.0 before 49.0.1 Fuel Accounting Bypass DoS27Monitor
- ← EarlierCVE-2026-115391Oct 22, 2026 · Wasmtime 46.0.0 before 46.0.3 and 47.0.0 before 47.0.4 Unbounded Heap Allocation via WASIp3 Streams27Monitor
- Later →CVE-2026-115393Oct 22, 2026 · Wasmtime before 24.0.12, 25.0.0 before 36.0.13, 37.0.0 before 46.0.2, and 47.0.0 before 47.0.3 Cross-Engine Type Confusion4Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| bytecodealliance wasmtime | 24.0.13 | Vendor (CNA) |
| bytecodealliance wasmtime | 36.0.14 | Vendor (CNA) |
| bytecodealliance wasmtime | 46.0.3 | Vendor (CNA) |
| bytecodealliance wasmtime | 47.0.4 | Vendor (CNA) |
| azl3 rpm-ostree 2024.4-11 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| crates.io:wasmtime | 24.0.13 | Package registry (OSV) |
| crates.io:wasmtime | 36.0.14 | Package registry (OSV) |
| crates.io:wasmtime | 46.0.3 | Package registry (OSV) |
| crates.io:wasmtime | 47.0.4 | Package registry (OSV) |
| debian:rust-wasmtime | 36.0.20+dfsg-1 · Debian:14 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 14, 2026+23 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-1186886 days apartWasmtime before 36.0.18, 37.0.0 before 48.0.6, and 49.0.0 before 49.0.3 Sandbox Escape via Symlink Rename35Monitor
Not on record for this CVE: patch commit or PR link · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-61 · UNIX Symbolic Link (Symlink) FollowingCVSS 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- SSVC exploitation— → none
- Fix✗ → ✓
- Exploit maturity— → none
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.