cve.bz

CVE-2026-115384 bytecodealliance wasmtime: Improper Input Validation

9.4 criticalEPSS 0.3%Fix available

Critical (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.

On this page
Wasmtime 39.0.0 before 48.0.4 and 49.0.0 before 49.0.2 contains a stack buffer overflow vulnerability that allows malicious guests to write ~16KB to the native stack via unvalidated async callback result types. Attackers can supply components with mistyped component-model-async callback functions to overwrite return addresses, crashing the host or escaping the sandbox.

Severity

CVSS 4.0

9.4 critical
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

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.3% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 24th 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-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • wasmtime (crates.io): fixed in 48.0.4, 49.0.2

Ask an AI about this CVE

Show the promptExplain 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.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
bytecodealliance wasmtimefrom 39.0.0 before 48.0.4
bytecodealliance wasmtimefrom 49.0.0 before 49.0.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
RUSTSEC-2026-0327crates.iowasmtime>=39.0.0 <48.0.4
>=49.0.0 <49.0.2
48.0.4, 49.0.2

Linux distributions

DistributionReleasePackageFixed inAdvisory
Ubuntu26.10rust-wasmtimeno fix listedUBUNTU-CVE-2026-115384
Azure Linux3cloud-hypervisorno fix listedAZL-111011
Azure Linux3openvmmno fix listedAZL-111026
Azure Linux3rustno fix listedAZL-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

Red Hat rates this Important.

Red Hat's statement

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.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Connectivity Link 1rhcl-1/wasm-shim-rhel9Not affected
Red Hat Enterprise Linux 10tree-sitterNot affected
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-115384.

Attack patterns (CAPEC)

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).

References

Check your stackJSON