Vulnerability Description
WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. In WAMR versions prior to 2.4.2, when running in LLVM-JIT mode, the runtime cannot exit normally when executing WebAssembly programs containing a memory.fill instruction where the first operand (memory address pointer) is greater than or equal to 2147483648 bytes (2GiB). This causes the runtime to hang in release builds or crash in debug builds due to accessing an invalid pointer. The issue does not occur in FAST-JIT mode or other runtime tools. This has been fixed in version 2.4.2.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Bytecodealliance | Webassembly Micro Runtime | < 2.4.2 |
Related Weaknesses (CWE)
References
- https://github.com/bytecodealliance/wasm-micro-runtime/commit/95f506a6e77d3ac758Patch
- https://github.com/bytecodealliance/wasm-micro-runtime/security/advisories/GHSA-ExploitThird Party Advisory
- https://github.com/bytecodealliance/wasm-micro-runtime/security/advisories/GHSA-ExploitThird Party Advisory
FAQ
What is CVE-2025-58749?
CVE-2025-58749 is a vulnerability with a CVSS score of 5.3 (MEDIUM). WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. In WAMR versions prior to 2.4.2, when running in LLVM-JIT mode, the runtime cannot exit normally when executing...
How severe is CVE-2025-58749?
CVE-2025-58749 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2025-58749?
Check the references section above for vendor advisories and patch information. Affected products include: Bytecodealliance Webassembly Micro Runtime.