Process crash via unhandled SIMD store opcode
Published Nov 25, 2025 · Updated Nov 26, 2025
Improper exceptional-condition handling in WAMR before 2.4.4 allows local users to crash iwasm with a crafted WebAssembly module. The classic interpreter's per-instance running-mode path fails to reject a v128.store SIMD opcode and reaches an unhandled null-address fault. Exploitation requires user interaction and classic interpreter mode; the demonstrated consequence is termination of the iwasm process.
Summary
What happened
Improper exceptional-condition handling in WAMR before 2.4.4 allows local users to crash iwasm with a crafted WebAssembly module. The classic interpreter's per-instance running-mode path fails to reject a v128.store SIMD opcode and reaches an unhandled null-address fault. Exploitation requires user interaction and classic interpreter mode; the demonstrated consequence is termination of the iwasm process.
The record
- CVE
- CVE-2025-64704
- Published
- Nov 25, 2025
- Updated
- Nov 26, 2025
- Vendor
- Bytecode Alliance
- Product
- WebAssembly Micro Runtime (WAMR)
- Classifications
- CWE-754, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 25, 2025CVE publishedPublication date reported by the CVE source.
- Nov 26, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.4.4
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- 0_v128.wasm proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo