CVE-2024-34249: wasm3 · n/a
Affects wasm3Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 May 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
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubwasm3/wasm3pkg:github/wasm3/wasm3Other 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
1. Immediately audit all deployments of wasm3 v0.5.0 and related versions to identify affected systems. 2. Restrict wasm3 usage to trusted and validated WebAssembly modules only, employing strict input validation and sandboxing techniques. 3. Implement runtime memory safety checks and monitoring to detect abnormal behavior or crashes related to wasm3 processes. 4. Where possible, isolate wasm3 execution environments using containerization or virtualization to limit potential damage from exploitation. 5. Monitor security advisories for official patches or updates from wasm3 maintainers and apply them promptly once available. 6. Employ network-level protections such as firewalls and intrusion detection systems to detect and block suspicious traffic targeting wasm3 services. 7. Conduct regular security assessments and fuzz testing on wasm3 integrations to uncover and remediate similar memory corruption issues proactively. 8. Educate developers and system administrators about secure WebAssembly practices and the risks of unsafe memory operations.
Description
wasm3 v0.5.0 was discovered to contain a heap buffer overflow which leads to segmentation fault via the function "DeallocateSlot" in wasm3/source/m3_compile.c.