Advisory record · GHSA-mq9p-qw76-q6h7

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.

CVSS 9.8 CriticalCriticalEPSS 0.0070 · 54th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 6 May 2024, 15:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
pywasm3PyPI<=0.5.0No fixed version yet
Identifiers
GHSA-mq9p-qw76-q6h7 · CVE-2024-34249 · PYSEC-2024-308
Weakness (CWE)
CWE-122
Published
6 May 2024
Updated
10 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The pywasm3 package, versions 0.5.0 and earlier, is affected by a heap buffer overflow in the DeallocateSlot function of the wasm3 runtime that it bundles. The source gives few details on how an attacker would trigger it, but it reports that the flaw causes a segmentation fault. No fixed version is listed, and no workaround is given.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H OSV
  • CISA KEV Not listed.
  • EPSS 0.0070, the 54th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 6 May 2024. New records show when each source confirmed them.

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.