CVE
CVE-2026-115893
- First Reported
- Oct 26, 2026
- Latest Reported
- Oct 27, 2026
CVE Enrichment
- CVSS
- 9.9 CRITICAL
- EPSS
- 0.43%
- EPSS Percentile
- 37.30%
- CISA KEV
- Not listed
Description
Wasmtime is a runtime for WebAssembly. Prior to 36.0.19, 48.0.7, and 49.0.4, the Cranelift compiler backend on aarch64 can compile a Wasm br_table instruction with more than approximately 256,000 targets so that it has an incorrect conditional branch target. The branch can then jump to arbitrary other code at a user-controlled offset, allowing a user-controlled Wasm module to escape the sandbox on aarch64 engines using the default Cranelift backend. This issue is fixed in versions 36.0.19, 48.0.7, and 49.0.4.
Technical Details
- CVSS Version
- 3.1
- CNA / NVD Source
- [email protected]
- Published
- 24-Oct-2026 05:16
- Last Modified
- 24-Oct-2026 05:16
- EPSS Date
- 2026-10-26
- CWE
- CWE-691
CVSS Vector
CVSS:3.1 AV:N /
AC:L /
PR:L /
UI:N /
S:C /
C:H /
I:H /
A:H
References
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.
Reported Context (2)
- Two critical Wasmtime sandbox escape flaws, CVE-2026-115889 and CVE-2026-115893, let a crafted WebAssembly (Wasm) module push the Cranelift compiler into generating unsafe machine code. Critical Wasmtime Flaws Could Enable WebAssembly Sandbox Escapes
- ARM64 hosts that updated to 36.0.7, 42.0.2, or 43.0.1 in April to fix an earlier Cranelift sandbox escape on ARM64 are still affected by CVE-2026-115893. Two Critical Wasmtime Flaws Could Enable WebAssembly Sandbox Escape
CVE (2)
People (2)
Vendors (2)
Products (2)
Tools (2)
Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.
