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

wasm3 uncontrolled memory allocation vulnerabilityGHSA-fmq6-4w57-2w3v

HIGHFix: wasm3/wasm3#490

GHSA-fmq6-4w57-2w3v is a high-severity (CVSS 8.4) Out-of-bounds Read vulnerability in wasm3. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Also known asCVE-2024-27529PYSEC-2024-305
Published
Updated
Affected
3 pkgs
Patched
See advisory
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
  • A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-fmq6-4w57-2w3v.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk
0.00%0.26%0.51%0.77%0.2%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

3 pkgs affected
🦀wasm3🐍pywasm3📦github.com/shareup/wasm-interpreter-apple

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

Description

wasm3 at commit 139076a contains a memory leak in the Read_utf8 function.

Affected Packages

3 total
EcosystemPackageVulnerable rangeFix
🦀crates.iowasm3all versionsNo fix
🐍PyPIpywasm3all versionsNo fix
📦SwiftURLgithub.com/shareup/wasm-interpreter-appleall versionsNo fix

Affected Products

1 product · 1 configurations
Application
wasm3wasm3_project
1 version
139076a

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 GHSA-fmq6-4w57-2w3v. 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 at commit 139076a contains a memory leak in the Read_utf8 function.
O3 Security · Impact-Aware SCA

Is GHSA-fmq6-4w57-2w3v in your dependencies?

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

GHSA-fmq6-4w57-2w3v: wasm3 (High 8.4)