CVE-2026-34946 json
Wasmtime's host panics when Winch compiler executes `table.fill`
published 2026-04-09 7 mo ago modified 2026-10-26 13 d ago also EUVD-2026-21025 , GHSA-q49f-xg75-m9xw , JLSEC-2026-1359 , RUSTSEC-2026-0089
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 31%
- public exploits
- 0
- none known
Summary
Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime's Winch compiler contains a vulnerability where the compilation of the table.fill instruction can result in a host panic. This means that a valid guest can be compiled with Winch, on any architecture, and cause the host to panic. This represents a denial-of-service vulnerability in Wasmtime due to guests being able to trigger a panic. The specific issue is that a historical refactoring changed how compiled code referenced tables within the table.* instructions. This refactoring forgot to update the Winch code paths associated as well, meaning that Winch was using the wrong indexing scheme. Due to the feature support of Winch the only problem that can result is tables being mixed up or nonexistent tables being used, meaning that the guest is limited to panicking the host (using a nonexistent table), or executing spec-incorrect behavior and modifying the wrong table. This vulnerability is fixed in 36.0.7, 42.0.2, and 43.0.1.
Patch / fix
- crates.io wasmtime 36.0.7, 42.0.2, 43.0.1
- julia Wasmtime_jll 45.0.1+0
- bytecodealliance wasmtime 36.0.7, 42.0.2, 44.0.1
- rust-wasmtime Debian 14 36.0.7+dfsg-1
debian advisories DEBIAN-CVE-2026-34946
- github.com/bytecodealliance/wasmtime#13010 pull request
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-34946 updated cvss 5.3
wasmtime: Wasmtime: Denial of Service via WebAssembly compilation error
-
Red Hat Connectivity Link 1 redhat-user-workloads/api-management-tenant/rhcl-1-3-wasm-shimaffected: workaround, no fix available
-
Red Hat Enterprise Linux 10 virt-firmware-rsnot affected: component not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7 mo ago
Exploit prediction
0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 5.9 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 4.0 | 5.9 | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/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 | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | wasmtime | >=25.0.0, <36.0.7 >=37.0.0, <42.0.2 >=43.0.0, <43.0.1 >=0.0.0-0, <36.0.7 |
36.0.7 42.0.2 43.0.1 |
| julia | Wasmtime_jll | >=39.0.0+0, <45.0.1+0 |
45.0.1+0 |
Affected products
- bytecodealliance wasmtime
Classification
References
-
github.com
/bytecodealliance/wasmtime/pull/13010
web
-
github.com
/bytecodealliance/wasmtime/security/advisories/GHSA-q49f-xg75-m9xw
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-34946
advisory, web
-
github.com
/bytecodealliance/wasmtime
package
-
rustsec.org
/advisories/RUSTSEC-2026-0089.html
web, advisory
-
github.com
/advisories/GHSA-q49f-xg75-m9xw
web
-
crates.io
/crates/wasmtime
package
Sources
- CVE List CVE-2026-34946
- GitHub Advisory GHSA-q49f-xg75-m9xw
- NVD CVE-2026-34946
- OSV JLSEC-2026-1359
- OSV RUSTSEC-2026-0089
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.