NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀
🦀 crates.io🐍 PyPI
Not in CISA KEV
MEDIUM severity

CVE-2022-34529 — wasm3

MEDIUM

CVE-2022-34529 is a medium-severity (CVSS 5.5) Out-of-bounds Read vulnerability in wasm3. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

WASM3 segmentation fault

Also known asGHSA-gq4p-4hxv-5rg9PYSEC-2022-43057
Published
Updated
Affected
2 pkgs
Patched
See advisory
Exploits
1 known
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk-0.00%
Lower risk than most CVEs21th percentile — riskier than 21% of all scored CVEsHighest risk
0.00%0.26%0.52%0.79%0.0%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🦀wasm3🐍pywasm3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io, PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

2 total
EcosystemPackageVulnerable rangeFix
🦀crates.iowasm3all versionsNo fix
🐍PyPIpywasm3all versionsNo fix

Affected Products

1 product · 1 configurations
Application
wasm3wasm3_project
1 version
0.5.0
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

WASM3 v0.5.0 was discovered to contain a segmentation fault via the comp…

github.comNVDAug 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wasm3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Remediation status

    The records we use list no patched version of wasm3 for CVE-2022-34529. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

  3. Mitigate without a patch

    Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.

Frequently Asked Questions

WASM3 v0.5.0 was discovered to contain a segmentation fault via the component Compile_Memory_CopyFill.
O3 Security · Impact-Aware SCA

Is CVE-2022-34529 in your dependencies?

Find it across crates.io, PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2022-34529: wasm3: WASM3 segmentation fault