Security fix · CVE-2025-58749
WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime.
Published Sep 16, 2025 · catalog updated Sep 16, 2025 · WebAssembly Micro Runtime (WAMR)
Last checked Oct 29, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2025-58749. EPSS is 0.37%. Act only if a listed version of WebAssembly Micro Runtime (WAMR) is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (WebAssembly Micro Runtime (WAMR)).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2025-64713 · Medium
- CVE-2025-64704 · Medium
- CVE-2025-43853 · High
- Severity
- Low2.1
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.37%
- Remediation
- Version ranges on file
- Affected products
- vendor bytecodealliance wasm-micro-runtime < 2.4.2
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor bytecodealliance wasm-micro-runtime < 2.4.2< 2.4.2
How to fix CVE-2025-58749
Upgrade
CVE-2025-58749 lists a fix boundary at 2.4.2. Compare the installed build with that boundary before you change production.
Version check
Affected < 2.4.2
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2025-58749. EPSS is 0.37%. Act only if a listed version of WebAssembly Micro Runtime (WAMR) is installed.
Which versions are affected?
Compare what you have installed with bytecodealliance wasm-micro-runtime < 2.4.2 < 2.4.2. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.37%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Sep 16, 2025 · EUVD
Detected
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 rele
Sep 16, 2025 · EUVD
Updated
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 rele
Sources
- CVE.orgVulnerability recordCVE-2025-58749
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2025-58749
30-day exploitation probability 0.37%
first.org - EUVDVulnerability recordEUVD-2025-29631
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 opera
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Oct 29, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSOct 29, 2026
- CVE.orgOct 23, 2026
- EUVDOct 23, 2026