What’s Vulnerable › Vulnerabilities
CVE-2025-64713: WebAssembly Micro Runtime frame_offset_bottom array bounds overflow in fast Interpreter mode when handling GET_GLOBAL(I32) followed by if opcode
- Severity: high (CVSS 7.4 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.4% probability of exploitation in the next 30 days
- Public exploit or detection template: yes
- Published: 2025-11-25 · updated 2026-10-18
- Weakness: CWE-119
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.
Affected products
- bytecodealliance wasm-micro-runtime: before 2.4.4 — fixed in 2.4.4
How to fix
Upgrade to a fixed version: bytecodealliance wasm-micro-runtime 2.4.4. Check the vendor advisory for mitigations.
References
- https://github.com/bytecodealliance/wasm-micro-runtime/releases/tag/WAMR-2.4.4
- https://github.com/bytecodealliance/wasm-micro-runtime/security/advisories/GHSA-gvx3-gg3x-rjcx
Get alerted when CVE-2025-64713 or the next vulnerability affects your stack