CVE-2024-25431: bytecodealliance wasm-micro-runtime · Out-of-bounds Read
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate CVE-2024-25431, organizations should immediately update their wasm-micro-runtime to the fixed version that includes commit 06df58f or later. If updating is not immediately possible, implement strict input validation and sanitization on all WebAssembly modules before loading them into the runtime. Employ sandboxing and least privilege principles to limit the runtime's access to system resources, reducing the impact of potential exploitation. Monitor and restrict the sources from which WebAssembly files can be loaded, and apply network-level controls to detect and block suspicious payloads. Incorporate runtime behavior monitoring to detect anomalies indicative of exploitation attempts. Educate users about the risks of loading untrusted WebAssembly files to reduce the likelihood of user interaction-based exploitation. Finally, maintain an incident response plan tailored to WebAssembly runtime compromises to enable rapid containment and recovery.
Description
An issue in bytecodealliance wasm-micro-runtime before v.b3f728c and fixed in commit 06df58f allows a remote attacker to escalate privileges via a crafted file to the check_was_abi_compatibility function.