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 a 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 products
wasm3_project: wasm3
References7
- github.com/wasm3/wasm3/issues/543 ExploitIssue Tracking
- github.com/wasm3/wasm3/issues/547 ExploitIssue Tracking
- github.com/wasm3/wasm3/
- vuldb.com/?ctiid.339334 Permissions RequiredVDB Entry
- vuldb.com/?id.339334 Third Party AdvisoryVDB Entry
- vuldb.com/?submit.719829 Third Party AdvisoryVDB Entry
- vuldb.com/?submit.719831 Third Party AdvisoryVDB Entry
Metrics
- CVSS 3.1
-
7.8
HIGH
Score source: NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - CVSS 4.0
-
1.9
LOW
Score source: CNA
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/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 - EPSS — exploit probability
- 0% percentile: 10 · as of 11 November 2026
- CWE
- CWE-119CWE-787
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.