CVE-2025-15413

wasm3 m3_exec.h op_CallIndirect memory corruption

HIGH
7.8
CVSS Score
Published: January 1, 2026 at 09:02 PM UTC
Updated: October 14, 2026 at 07:10 PM UTC
1 product affected across 1 vendorWASM3

Using wasm3 by N/A?

Get instant alerts when new vulnerabilities affect wasm3 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%
SSVC
PoC

Description

A vulnerability was detected in wasm3 up to 0.5.0. Impacted is the function op_SetSlot_i32/op_CallIndirect of the file m3_exec.h. Performing manipulation results in memory corruption. The attack needs to be approached locally. The exploit is now public and may be used. Unfortunately, the project has no active maintainer at the moment.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

References (7)

SignaturePermissions RequiredVDB Entry
https://vuldb.com/?ctiid.339334
VDB EntryTechnical DescriptionThird Party Advisory
https://vuldb.com/?id.339334
Third Party AdvisoryVDB Entry
https://vuldb.com/?submit.719829
Third Party AdvisoryVDB Entry
https://vuldb.com/?submit.719831
Product
Source: cverecord
https://github.com/wasm3/wasm3/

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-119CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card