Bytecode Alliance Wasmtime Flaw CVE-2026-115893: Update Now
Published November 5, 2026 · Last updated November 5, 2026
The short version: CVE-2026-115893 is a critical-severity security flaw in Bytecode Alliance Wasmtime. The National Vulnerability Database (NVD) published it on October 23, 2026, and the score it lists is 9.9 out of 10. When FraudMeNot checked on November 5, 2026, CISA had not added CVE-2026-115893 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.
What the official record says about CVE-2026-115893
The record was filed by github.com. In its own words: "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."
Why Wasmtime admins should care
Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on github.com rated CVE-2026-115893 9.9 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker needs a low-privilege account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Wasmtime running is high. Scoring string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
Affected Wasmtime releases
According to the record, these releases are vulnerable:
- version < 36.0.19
- version >= 37.0.0, < 48.0.7
- version >= 49.0.0, < 49.0.4
The type of bug behind CVE-2026-115893
NVD classifies it using MITRE's Common Weakness Enumeration:
- CWE-691, Insufficient Control Flow Management. MITRE describes this class of bug as follows: "The code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways."
Vendor remediation for CVE-2026-115893
The vendor advisory remediation for operators of Wasmtime, quoted for this page, is: "Upgrade the wasmtime crate to 36.0.19 or later on the 36.x line, 48.0.7 or later on 37–48.x, or 49.0.4 or later on 49.x (GHSA-mghf-wjfp-p5xm)."
What to do about it
- Update now: Upgrade the wasmtime crate to 36.0.19 or later on the 36.x line, 48.0.7 or later on 37–48.x, or 49.0.4 or later on 49.x (GHSA-mghf-wjfp-p5xm).
- Who should act: IT teams, managed service providers, and developers who run or ship Wasmtime. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
- Read the official advisory from Bytecode Alliance (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
- After patching, confirm the new version is actually running and review logs from October 23, 2026 onward for anything unusual.
- Home users: you do not need to buy or download anything because of CVE-2026-115893. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.
CVE-2026-115893 record details from CISA and NVD
- Attack complexity for CVE-2026-115893: low
- CVE-2026-115893 CVSS scope: changed
- NVD sub-scores for CVE-2026-115893: exploitability 3.1, impact 6.0.
- Who mapped the weakness type: the address listed on github.com (Secondary)
- References in the NVD record: 12.
- CISA SSVC decision points for CVE-2026-115893 (from NVD): exploitation=none; automatable=no; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).
Dates to know
- October 23, 2026: NVD publishes CVE-2026-115893.
- November 5, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-115893 is not listed.
- October 29, 2026: most recent NVD update (record status: Deferred).
Official references
Links listed in the NVD record (labels in brackets come from NVD):
- github.com/bytecodealliance/wasmtime/commit/222ff3a65dab9aa7011f8c246937751a0bac5abd
- github.com/bytecodealliance/wasmtime/commit/994549891c8a706cb4f2809f9d17b9f67b31e618
- github.com/bytecodealliance/wasmtime/commit/e61df1b454be9313d61a5f8de07722a421139bbe
- github.com/bytecodealliance/wasmtime/commit/f517bd6e890c7c1291ab9fe05d8cc0c9f11e56aa
- github.com/bytecodealliance/wasmtime/pull/14818
- github.com/bytecodealliance/wasmtime/pull/14819
- github.com/bytecodealliance/wasmtime/pull/14820
- github.com/bytecodealliance/wasmtime/pull/14826
Sources
- NVD: CVE-2026-115893
- CVE.org: CVE-2026-115893
- Bytecode Alliance advisory
- Bytecode Alliance advisory
- Bytecode Alliance advisory
- MITRE CWE-691
General education only, not security advice. Facts checked against the sources above on the date shown.