bytecodealliance wasm-micro-runtime up to 2.4.3 memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in bytecodealliance wasm-micro-runtime up to 2.4.3. It has been declared as critical. This impacts an unknown function. Such manipulation leads to memory corruption. This vulnerability is traded as CVE-2025-64713. An attack has to be approached locally. There is no exploit available. It is recommended to upgrade the affected component.
Details
A vulnerability was found in bytecodealliance wasm-micro-runtime up to 2.4.3. It has been rated as problematic. Affected by this issue is some unknown processing. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is availability. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability is handled as CVE-2025-64713 since 11/10/2025. The exploitation is known to be difficult. The attack needs to be approached locally. There are neither technical details nor an exploit publicly available.
Upgrading to version 2.4.4 eliminates this vulnerability. The upgrade is hosted for download at github.com.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 5.0
VulDB Base Score: 2.5
VulDB Temp Score: 2.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.4
NVD Vector: 🔒
CNA Base Score: 5.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: wasm-micro-runtime 2.4.4
Timeline
11/10/2025 CVE reserved11/26/2025 Advisory disclosed
11/26/2025 VulDB entry created
12/04/2025 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-gvx3-gg3x-rjcx
Status: Confirmed
CVE: CVE-2025-64713 (🔒)
GCVE (CVE): GCVE-0-2025-64713
GCVE (VulDB): GCVE-100-333584
Entry
Created: 11/26/2025 06:55Updated: 12/04/2025 04:26
Changes: 11/26/2025 06:55 (65), 12/04/2025 04:26 (11)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.