CVSS 4.0
9.4 criticalCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HCritical (9.4) in bytecodealliance wasmtime. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in wasmtime 48.0.4, 49.0.2.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:Hwasmtime (crates.io): fixed in 48.0.4, 49.0.2Explain CVE-2026-115384 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-115384?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-115384?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-115384 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 | from 39.0.0 before 48.0.4 |
| bytecodealliance wasmtime | from 49.0.0 before 49.0.2 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| RUSTSEC-2026-0327 | crates.io | wasmtime | >=39.0.0 <48.0.4 >=49.0.0 <49.0.2 | 48.0.4, 49.0.2 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Ubuntu | 26.10 | rust-wasmtime | no fix listed | UBUNTU-CVE-2026-115384 |
| Azure Linux | 3 | cloud-hypervisor | no fix listed | AZL-111011 |
| Azure Linux | 3 | openvmm | no fix listed | AZL-111026 |
| Azure Linux | 3 | rust | no fix listed | AZL-111077 AZL-111086 |
From the distributions' data via OSV.dev: 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: Ubuntu.
Red Hat rates this Important.
This vulnerability is rated as Important severity because an attacker capable of executing guest code within Wasmtime can escape the containment boundary and achieve host-level execution or crash the host process. While Red Hat environments rarely expose WebAssembly runtimes directly to unauthenticated network users, workloads that process untrusted guest modules are directly at risk. Exploitation requires the attacker to have existing privileges or submission capabilities to run custom components utilizing asynchronous callback interfaces.
Only execute verified WebAssembly components and isolate the runtime process using system sandboxing.
Operational controls:
1. Restrict execution to trusted, vetted WebAssembly components. Avoid loading or executing unverified third-party components that define asynchronous callback functions.
2. If untrusted modules must be evaluated, run the host runtime process inside an unprivileged container (such as Podman) or apply systemd service sandboxing options (such as `ProtectSystem=strict`, `NoNewPrivileges=yes`, and seccomp filters) to restrict host access in the event of a sandbox escape.
Caveats:
Limiting guest code to trusted sources restricts multi-tenant or dynamic plugin capabilities. Operating within an isolated container or restricted systemd environment may require adjustments to host filesystem permissions and mounts, and does not prevent a denial of service crash of the isolated runtime process.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Connectivity Link 1 | rhcl-1/wasm-shim-rhel9 | Not affected | |
| Red Hat Enterprise Linux 10 | tree-sitter | Not 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-115384.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).