cve.bz

CVE-2026-115889 bytecodealliance wasmtime: Numeric Truncation Error

9.9 criticalEPSS 0.5%Fix available

Critical (9.9) in bytecodealliance wasmtime. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in wasmtime 36.0.19, 43.0.0.

On this page
Wasmtime is a runtime for WebAssembly. Prior to 36.0.19 and 43.0.0, the Cranelift compiler backend bit-packs SSA value indices in a way that can silently overflow in release builds when compiling a sufficiently large or specially crafted Wasm function with many SSA values. The overflow can make Cranelift reference incorrect IR values, causing arbitrary miscompilation, type confusion, and other attacker-controlled effects that may escape the Wasm sandbox on any architecture using the default Cranelift backend. This issue is fixed in versions 36.0.19 and 43.0.0.

Severity

CVSS 3.1

9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 40th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-26. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-197 Numeric Truncation Error
CWE-843 Access of Resource Using Incompatible Type (Type Confusion)
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-115889 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-115889?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-115889?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-115889 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
bytecodealliance wasmtime< 36.0.19
bytecodealliance wasmtime>= 37.0.0, < 43.0.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-897f-g5gm-fmxmcrates.iowasmtime<36.0.1936.0.19
GHSA-897f-g5gm-fmxmcrates.iowasmtime>=37.0.0 <43.0.043.0.0
RUSTSEC-2026-0380crates.iowasmtime>=0.0.0-0 <36.0.19
>=37.0.0 <43.0.0
36.0.19, 43.0.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian13rust-wasmtimeno fix listedDEBIAN-CVE-2026-115889
Debian14rust-wasmtime36.0.20+dfsg-1DEBIAN-CVE-2026-115889
Ubuntu24.04:LTS, 26.04:LTS, 26.10rust-wasmtimeno fix listedUBUNTU-CVE-2026-115889
Azure Linux3rust1.75.0-31AZL-111431
Azure Linux3rust1.98.1-1AZL-111437

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

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important severity because an untrusted guest WebAssembly payload can break sandbox boundaries and gain full host system access. While triggering the issue requires supplying an extraordinarily complex or specially structured module, the ability to achieve sandbox breakout without administrative privileges warrants an Important rating. In Red Hat environments, the primary risk lies in multi-tenant or serverless hosting configurations where untrusted WebAssembly binaries are accepted and executed.

Red Hat's mitigation

Restrict execution to trusted WebAssembly modules and avoid processing unvalidated binaries from untrusted sources. If the runtime must process untrusted modules, deploy the hosting application inside an operating system-level sandbox or container (such as Podman or a systemd service unit configured with strict seccomp filtering, unprivileged user namespaces, and read-only filesystem mounts) to contain a potential sandbox breakout.

Caveats: Additional host-level sandboxing introduces operational overhead and may restrict legitimate host system interactions or inter-process communication required by the guest application.

--- 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 enforce bounds on WebAssembly function complexity and SSA value counts before Cranelift compilation to avoid exceeding the 24-bit value index threshold: upgrade to Wasmtime 36.0.19 and 43.0.0 (or the fixed Rhcl 1/Wasm Shim Rhel/Tree Sitter/Virt Firmware Rs builds), which replace the 24-bit bit-packed encoding in ValueDataPacked with full 32-bit fields in a 10-byte struct to prevent value index truncation, closing crafted WebAssembly module with a function containing an excessive number of SSA values. Until patched, this is a concern on Multi-tenant or serverless hosts running release builds of Wasmtime configured with the Cranelift compiler backend, so Restrict execution to trusted WebAssembly modules and isolate the hosting application within an operating system container or service unit configured with strict seccomp filtering, unprivileged user namespaces, and read-only mounts. As a compensating measure, Restrict or disable JIT compilation pipelines to prevent type confusion and arbitrary code execution arising from JIT miscompilation, Deploy EDR agents to detect anomalous host-level process execution and lateral movement following an escape from the WebAssembly sandbox, and Monitor runtime system calls with Falco or eBPF to detect suspicious host system calls, unexpected child process spawns, and unauthorized file access. These controls limit blast radius and contain exploitation, but they do not fix the underlying silent integer truncation defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-1311 Input Size and Quantity Bounds Enforcement (high)

ProductPackageStateAdvisory
Red Hat Connectivity Link 1rhcl-1/wasm-shim-rhel9Affected
Red Hat Enterprise Linux 10tree-sitterAffected
Red Hat Enterprise Linux 10virt-firmware-rsNot 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-115889.

References

Check your stackJSON