WASM3 segmentation fault

published 2022-07-27 4 y ago modified 2026-06-17 4 mo ago also GHSA-gq4p-4hxv-5rg9 , PYSEC-2022-43057 , EUVD-2022-0223

cvss: 5.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 21%
public exploits: 0; none known

WASM3 v0.5.0 was discovered to contain a segmentation fault via the component Compile_Memory_CopyFill.

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/wasm3/wasm3/issues/337 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
GitHub	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
OSV	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem	package	affected	fixed in
pypi	pywasm3	<=0.5.0 all versions	no fix listed
crates.io	wasm3	<=0.5.0	no fix listed

Classification

Weakness

CWE-125 Out-of-bounds Read
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

github.com /wasm3/wasm3/issues/337
web, exploit, issue-tracking, third-party-advisory, evidence, report
nvd.nist.gov /vuln/detail/CVE-2022-34529
advisory
github.com /pypa/advisory-database/tree/main/vulns/pywasm3/PYSEC-2022-43057.yaml
web
github.com /advisories/GHSA-gq4p-4hxv-5rg9
advisory

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary