Skip to content
Fencer Intel
low 3.8

CVE-2026-115393 json

Wasmtime before 24.0.12, 25.0.0 before 36.0.13, 37.0.0 before 46.0.2, and 47.0.0 before 47.0.3 Cross-Engine Type Confusion

published 3mo ago modified 11d ago also EUVD-2026-108327 , GHSA-hgjw-h833-99q9 , RUSTSEC-2026-0222

cvss
3.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.1%
EPSS 0.1% chance of exploitation in 30 days, percentile 0%
public exploits
0
none known

Summary

Wasmtime before 24.0.12, 25.0.0 before 36.0.13, 37.0.0 before 46.0.2, and 47.0.0 before 47.0.3 contains a type confusion vulnerability because several Store APIs fail to validate that objects belong to the Store's Engine. Embedders mixing objects between Engines via Instance::new, StructRefPre::new, or Tag::new can trigger trampoline signature mismatches causing out-of-bounds stack writes, GC heap corruption, or panics.

Patch / fix

  • crates.io wasmtime 24.0.12, 36.0.13, 46.0.2, 47.0.3
  • bytecodealliance wasmtime 24.0.12, 36.0.13, 46.0.2, 47.0.3
  • rust-wasmtime Debian 14 36.0.13+dfsg-1

debian advisories DEBIAN-CVE-2026-115393

Is CVE-2026-115393 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-115393 updated cvss 3.8

wasmtime: wasmtime: Memory corruption via cross-engine object validation failure

  • Red Hat Connectivity Link 1 rhcl-1/wasm-shim-rhel9 Red Hat Enterprise Linux 10 tree-sitter 0.23.0-3.el10, virt-firmware-rs 26.4-1.el10
    affected: no fix available “Fix deferred”

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
11d ago

Exploit prediction

0.09% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 1.0 CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
CNA 3.1 3.8 CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L
CNA 4.0 1.0 CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:P/VC:L/VI:L/VA:L/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
OSV 3.1 3.8 CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
crates.io wasmtime
>=0.0.0-0, <24.0.12
>=25.0.0, <36.0.13
>=37.0.0, <46.0.2
>=47.0.0, <47.0.3
24.0.12
36.0.13
46.0.2
47.0.3

Affected products

  • bytecodealliance wasmtime

Classification

Weakness

References

Sources

Fencer Intel 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.