CVE-2025-15412: WebAssembly wabt · Out-of-Bounds Read
Affects WebAssembly wabtSource CVE Database V5
Not known to be exploited · CVSS 4.8 Medium.
Data as of 25 Oct 2026, 19:02 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 1 Jan 2026
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 2026-10-25.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubwebassembly/wabtpkg:github/webassembly/wabtOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Given the absence of an official patch, organizations should implement strict access controls to limit local access to systems running wabt, especially the wasm-decompile tool. Use role-based access control (RBAC) and enforce least privilege principles to prevent untrusted users from executing the vulnerable component. Monitor and audit usage of wabt binaries to detect unusual or unauthorized activity. Consider isolating WebAssembly development and analysis environments from sensitive networks and data. If feasible, review the source code of wabt::Decompiler::VarName and develop an internal patch or workaround to validate input sizes and prevent out-of-bounds reads. Engage with the open-source community to contribute fixes or track any emerging patches. Additionally, containerizing the wabt tool with strict resource and memory limits can reduce the impact of potential crashes. Finally, educate developers and system administrators about the vulnerability and the importance of controlling local access to development tools.
Description
A security vulnerability has been detected in WebAssembly wabt up to 1.0.39. This issue affects the function wabt::Decompiler::VarName of the file /src/repro/wabt/bin/wasm-decompile of the component wasm-decompile. Such manipulation leads to out-of-bounds read. Local access is required to approach this attack. The exploit has been disclosed publicly and may be used. Unfortunately, the project has no active maintainer at the moment. In a reply to the issue report somebody recommended to the researcher to provide a PR himself.