CVE Intelligence
Low Memory corruption

CVE-2026-115393 — 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

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.

Published Oct 22, 2026 · Updated Oct 29, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.1% (30-day exploitation probability)+0

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.09%
ahead of 0% of scored CVEs · Oct 30, 2026
Affects
Bytecodealliance
Wasmtime
CVSS base
3.8
Low · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Bytecodealliance Wasmtime).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Bytecodealliance Wasmtime < 24.0.12≥ 25.0.0 and < 36.0.13≥ 37.0.0 and < 46.0.2≥ 47.0.0 and < 47.0.3 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
High
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
1.0 CVSS 4.0 Low — — disclosure@vulncheck.com via NIST National Vulnerability Database
1.0 CVSS 4.0 Low — — VulnCheck via CVE Program (cve.org) e CISA ADP
3.8 CVSS 3.1 Low 0.3 3.4 disclosure@vulncheck.com via NIST National Vulnerability Database
3.8 CVSS 3.1 Low — — GitHub, Inc. via GitHub Security Advisories
3.8 CVSS 3.1 Low — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-787 · Out-of-bounds Write

Other CVEs with this weakness →

EPSS over time FIRST

Oct 23, 2026 → Oct 30, 2026 · 8 reading(s) · max 0.09%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 29, 2026 · CVE Program (cve.org) e CISA ADP
  • Affected products added · bytecodealliance/wasmtime
    Oct 22, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 22, 2026
  • CVSS changed · 3.8
    Oct 22, 2026 · NIST National Vulnerability Database
  • Source status changed · → Deferred
    Oct 22, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 22, 2026 · Alertas do Telegram
  • CVE published
    Oct 22, 2026 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 2× References added · Oct 22, 2026 – Oct 29, 2026
  • 1× Official description updated · Oct 22, 2026 – Oct 22, 2026

References

4 on the record

Elsewhere on this site

Bytecodealliance
every CVE for this vendor
Memory corruption
same class
CWE-787
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-119140 Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 Host Panic via thread.yield 2d
  • CVE-2026-119137 Wasmtime 42.0.0 before 48.0.6 and 49.0.0 before 49.0.3 Stack Overflow via Type Registry 2d
  • CVE-2026-119141 Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 Host Panic via realloc 2d
  • CVE-2026-119142 Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 Host Panic via call_async Drop 2d
  • CVE-2026-119138 Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 Panic After Trap 2d
  • CVE-2026-119143 Wasmtime 46.0.0 before 48.0.6 and 49.0.0 before 49.0.3 Panic via Zero-Length Stream Writes 2d

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-115393 is "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", rated Low. It affects Wasmtime (Bytecodealliance); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 3.8 describes technical severity. EPSS 0.09% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.