CVSS 3.1
9.9 criticalCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HCritical (9.9) in bytecodealliance wasmtime. EPSS 1.0% estimated probability of exploitation activity in the next 30 days. Fixed in wasmtime 36.0.19, 48.0.7, 49.0.4.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:Hwasmtime (crates.io): fixed in 36.0.19, 48.0.7, 49.0.4Explain CVE-2026-115893 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-115893?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-115893?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-115893 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| bytecodealliance wasmtime | < 36.0.19 |
| bytecodealliance wasmtime | >= 37.0.0, < 48.0.7 |
| bytecodealliance wasmtime | >= 49.0.0, < 49.0.4 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-mghf-wjfp-p5xm | crates.io | wasmtime | <36.0.19 | 36.0.19 |
| GHSA-mghf-wjfp-p5xm | crates.io | wasmtime | >=37.0.0 <48.0.7 | 48.0.7 |
| GHSA-mghf-wjfp-p5xm | crates.io | wasmtime | >=49.0.0 <49.0.4 | 49.0.4 |
| RUSTSEC-2026-0379 | crates.io | wasmtime | >=0.0.0-0 <36.0.19 >=37.0.0 <48.0.7 >=49.0.0 <49.0.4 | 36.0.19, 48.0.7, 49.0.4 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 13 | rust-wasmtime | no fix listed | DEBIAN-CVE-2026-115893 |
| Debian | 14 | rust-wasmtime | 36.0.20+dfsg-1 | DEBIAN-CVE-2026-115893 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 | rust-wasmtime | no fix listed | UBUNTU-CVE-2026-115893 |
| Azure Linux | 3 | rust | 1.75.0-31 | AZL-111428 |
| Azure Linux | 3 | rust | 1.98.1-1 | AZL-111434 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.
Red Hat rates this Important.
Red Hat rates this vulnerability as Important because an attacker executing untrusted WebAssembly bytecode can bypass runtime sandbox restrictions and achieve arbitrary code execution in the context of the host process. The risk is constrained primarily to 64-bit ARM (aarch64) environments that evaluate untrusted or maliciously crafted modules containing unusually large multi-target branch tables. Deployments on other CPU architectures or those processing only verified, internal WebAssembly payloads are not exposed to this escape vector.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
--- CME Mitigation Guidance (2026-11-02) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to validate and bound the maximum number of targets allowed in WebAssembly br_table instructions before Cranelift compilation: upgrade to Wasmtime 36.0.19, 48.0.7, 49.0.4 (or the fixed Tree Sitter/Rhcl 1/Wasm Shim Rhel/Virt Firmware Rs builds), which append the default target to the end of the jump table and clamp out-of-bounds indices using a conditional select instruction instead of a conditional branch, closing crafted WebAssembly module with an oversized br_table instruction. Until patched, this is only a concern on 64-bit ARM (AArch64) hosts running Wasmtime with Cranelift compiling untrusted WebAssembly modules — deployments on non-AArch64 architectures or environments executing only verified internal WebAssembly payloads are unaffected — so restrict or audit the ingestion and execution of untrusted WebAssembly modules containing oversized br_table jump tables, or limit Cranelift compilation on AArch64 systems. As a compensating measure, restrict or disable JIT compilation via Cranelift for untrusted WebAssembly modules, deploy an EDR agent to monitor for anomalous host processes, unauthorized payloads, or sandbox escape activity, and use Falco or eBPF runtime security to detect unexpected system calls and host process spawning following runtime escape. These controls limit blast radius and contain exploitation, but they do not fix the underlying branch target offset wrapping defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-1311 Input Size and Quantity Bounds Enforcement (high)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Connectivity Link 1 | rhcl-1/wasm-shim-rhel9 | Affected | |
| Red Hat Enterprise Linux 10 | tree-sitter | Affected | |
| Red Hat Enterprise Linux 10 | virt-firmware-rs | Not affected |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-115893.
Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.