CVE-2025-15413: A vulnerability was detected in wasm3 up to 0.5.0

Q: How do I fix CVE-2025-15413?

wasm3: upgrade to newer than 0.5.0. Exact commands for each OS are on this page.

Q: Is CVE-2025-15413 being exploited?

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

Q: What does CVE-2025-15413 affect?

CVE-2025-15413 affects wasm3. Severity is medium (CVSS 5.3). A vulnerability was detected in wasm3 up to 0.5.0. Impacted is the function op_SetSlot_i32/op_CallIndirect of the file m3_exec.h. Performing a manipulation results in memory corruption. The attack needs to be approached locally. The exploit

Q: How urgent is CVE-2025-15413?

Priority 26/100. Public exploit reference

Routine

MEDIUM 5.3UPGRADE

CVE-2025-15413 is a medium-severity flaw (CVSS 5.3) affecting wasm3. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was detected in wasm3 up to 0.5.0. Impacted is the function op_SetSlot_i32/op_CallIndirect of the file m3_exec.h. Performing a manipulation results in memory corruption. The attack needs to be approached locally. The exploit is now public and may be used. Unfortunately, the project has no active maintainer at the moment.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 90%)
CISA exploited list	No
Weakness	CWE-119, CWE-787
Published	2026-01-01
Last modified	2026-10-14

Publisher (CNA): VulDB · Vendor: wasm3 project

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

Am I affected?

Timeline

2026-01-01 21:15 UTCPublished CVE record published
2026-10-14 19:10 UTCUpdated Record last modified

wasm3 project wasm3 UPGRADE

Affected: <= 0.5.0

Fixed in: newer than 0.5.0

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 0.5.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wasm3

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wasm3

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-2025-15413?

wasm3: upgrade to newer than 0.5.0. Exact commands for each OS are on this page.

Is CVE-2025-15413 being exploited?

CVE-2025-15413 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-2025-15413 affect?

CVE-2025-15413 affects wasm3. Severity is medium (CVSS 5.3). A vulnerability was detected in wasm3 up to 0.5.0. Impacted is the function op_SetSlot_i32/op_CallIndirect of the file m3_exec.h. Performing a manipulation results in memory corruption. The attack needs to be approached locally. The exploit

How urgent is CVE-2025-15413?

Priority 26/100. Public exploit reference

Related CVEs

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-34249 CRITICAL 9.8 DOWNGRADE wasm3 v0.5.0 was discovered to contain a heap buffer overflow which leads to segmentation fault via the functi
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