Bytecodealliance Wasm Micro Runtime
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Bytecodealliance Wasm Micro Runtime.
By the Year
In 2026 there have been 0 vulnerabilities in Bytecodealliance Wasm Micro Runtime. Last year, in 2025 Wasm Micro Runtime had 1 security vulnerability published. Right now, Wasm Micro Runtime is on track to have less security vulnerabilities in 2026 than it did last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 1 | 0.00 |
It may take a day or so for new Wasm Micro Runtime vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Bytecodealliance Wasm Micro Runtime Security Vulnerabilities
WAMR Memory.fill in LLVM-JIT Causes Hang/Crash <2.4.2
CVE-2025-58749
- September 16, 2025
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.
Untrusted Pointer Dereference
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Bytecodealliance Wasm Micro Runtime or by Bytecodealliance? Click the Watch button to subscribe.
