# CVE-2025-64713: Memory corruption in wasm-micro-runtime

> An out-of-bounds array access in WAMR's fast interpreter allows attackers to cause memory corruption, potentially leading to code execution or crashes.

- **Severity:** Medium 5.1 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Nov 2025
- **Updated:** 26 Nov 2025
- **Also known as:** GHSA-gvx3-gg3x-rjcx

## What is CVE-2025-64713?

CVE-2025-64713 is a medium-severity memory corruption vulnerability in bytecodealliance wasm-micro-runtime, published on 25 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. Prior to version 2.4.4, an out-of-bounds array access issue exists in WAMR's fast interpreter mode during WASM bytecode loading. When frame_ref_bottom and frame_offset_bottom arrays are at capacity and a GET_GLOBAL(I32) opcode is encountered, frame_ref_bottom is expanded but frame_offset_bottom may not be. If this is immediately followed by an if opcode that triggers preserve_local_for_block, the function traverses arrays using stack_cell_num as the upper bound, causing out-of-bounds access to frame_offset_bottom since it wasn't expanded to match the increased stack_cell_num. This issue has been patched in version 2.4.4.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Bytecodealliance Webassembly Micro Runtime.

## How do I fix CVE-2025-64713?

No fix has been published for CVE-2025-64713 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-64713 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64713 exists.

## Other vulnerabilities in bytecodealliance wasm-micro-runtime

- [CVE-2024-25431](https://insights.sbomify.com/CVE-2024-25431/): Memory corruption in n/a (high 8.8)
- [CVE-2024-27532](https://insights.sbomify.com/CVE-2024-27532/): Null dereference in n/a (high 7.5)
- [CVE-2024-34251](https://insights.sbomify.com/CVE-2024-34251/): Memory corruption in n/a (high 7.5)
- [CVE-2023-48105](https://insights.sbomify.com/CVE-2023-48105/): Memory corruption in n/a (high 7.5)
- [CVE-2025-43853](https://insights.sbomify.com/CVE-2025-43853/): iwasm vulnerable to filesystem sandbox escape with symlink when using uvwasi feature (high 7.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64713 is a medium-severity memory corruption vulnerability in bytecodealliance wasm-micro-runtime, published on 25 Nov 2025. 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-64713 exists.

Affected product: bytecodealliance wasm-micro-runtime. 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-64713/ (Markdown: https://insights.sbomify.com/CVE-2025-64713/index.md)
```

## Sources

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

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