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

- **Severity:** Medium 4.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jan 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-fgq8-gvxr-ghw7

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

Weakness: CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-15413?

It affects 1 product.


Products: 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.

## 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](https://insights.sbomify.com/CVE-2024-34249/): pywasm3 contains a heap buffer overflow which leads to segmentation fault (critical 9.8)
- [CVE-2024-27528](https://insights.sbomify.com/CVE-2024-27528/): pywasm3 has an Invalid Memory Read, Leading to DoS and Potential Code Execution (high 8.4)
- [CVE-2024-27529](https://insights.sbomify.com/CVE-2024-27529/): wasm3 uncontrolled memory allocation vulnerability (high 8.4)
- [CVE-2024-27530](https://insights.sbomify.com/CVE-2024-27530/): pywasm3 contains a Use-After-Free in ForEachModule (high 8.4)
- [CVE-2022-28990](https://insights.sbomify.com/CVE-2022-28990/): Buffer overflow in wasm3 (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15413 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15413 exists.

Affected product: wasm3. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15413/ (Markdown: https://insights.sbomify.com/CVE-2025-15413/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15413
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15413
- OSV: https://osv.dev/vulnerability/CVE-2025-15413

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15413/
Summaries are generated and may contain mistakes; the official description above is the record.