CVE-2025-15413 wasm3 m3_exec.h op_CallIndirect memory corruption
Local attackers can exploit memory corruption in wasm3 to execute arbitrary code or cause denial of service, with no active maintainer to provide a fix.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-15413?
CVE-2025-15413 is a medium-severity memory corruption vulnerability in wasm3, published on 1 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Official 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.
Which versions are affected by CVE-2025-15413?
It affects 1 product.
Products include Wasm3 Project Wasm3.
How do I fix CVE-2025-15413?
No fix has been published for CVE-2025-15413 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2025-15413 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15413 exists.
Other vulnerabilities in wasm3
- CVE-2024-34249 pywasm3 contains a heap buffer overflow which leads to segmentation fault
- CVE-2024-27528 pywasm3 has an Invalid Memory Read, Leading to DoS and Potential Code Execution
- CVE-2024-27529 wasm3 uncontrolled memory allocation vulnerability
- CVE-2024-27530 pywasm3 contains a Use-After-Free in ForEachModule
- CVE-2022-28990 Buffer overflow in wasm3
Sources
Also known as GHSA-fgq8-gvxr-ghw7.