CVE-2025-64713: WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. Prior to version 2.4.4, an…
CVE-2025-64713 · Severity: medium · CVSS 5.1 · Published 2025-11-25
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.
No. Junglewise Threat Intelligence has no report of CVE-2025-64713 being exploited in the wild.
How severe is CVE-2025-64713?
Medium severity, with a CVSS score of 5.1, published 25 November 2025.
Which products and versions are affected?
Bytecodealliance Webassembly Micro Runtime. The advisory does not name versions.
Is there a fix for CVE-2025-64713?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2025-64713?
Check whether you run Bytecodealliance Webassembly Micro Runtime. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.