CVE-2024-34249: wasm3 v0.5.0 was discovered to contain a heap buffer overflow which leads to segmentation fault via the functi

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2024-34249 is a critical-severity flaw (CVSS 9.8) affecting wasm3. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.7% (top 47%)
CISA exploited list	No
Weakness	CWE-122
Published	2024-05-06
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: wasm3 project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-05-06 15:15 UTCPublished CVE record published
2026-06-17 07:33 UTCUpdated Record last modified

wasm3 project wasm3 DOWNGRADE

Affected: 0.5.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.5.0

1. Check installed version

apt-cache policy wasm3 || rpm -q wasm3 || wasm3 --version

2. No fixed release: DOWNGRADE to a release before 0.5.0 (Debian / Ubuntu)

apt-cache madison wasm3 sudo apt install wasm3=<VERSION_BEFORE_0.5.0> sudo apt-mark hold wasm3

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list wasm3 sudo dnf downgrade wasm3-<VERSION_BEFORE_0.5.0> sudo dnf versionlock add wasm3

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2024-34249?

wasm3: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2024-34249 being exploited?

CVE-2024-34249 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2024-34249 affect?

CVE-2024-34249 affects wasm3. Severity is critical (CVSS 9.8). 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.

How urgent is CVE-2024-34249?

Priority 58/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-15413 MEDIUM 5.3 UPGRADE A vulnerability was detected in wasm3 up to 0.5.0
CVE-2025-15572 LOW 3.3 UPGRADE A vulnerability has been found in wasm3 up to 0.5.0
CVE-2024-34252 HIGH 7.5 DOWNGRADE wasm3 v0.5.0 was discovered to contain a global buffer overflow which leads to segmentation fault via the func
CVE-2024-34246 HIGH 7.5 DOWNGRADE wasm3 v0.5.0 was discovered to contain an out-of-bound memory read which leads to segmentation fault via the f
CVE-2024-27530 HIGH 8.4 DOWNGRADE wasm3 139076a contains a Use-After-Free in ForEachModule.

References

← Back to latest CVEs