Cyber Resilience

CVE-2025-15413

Memory Safety in Wasm3 Project Wasm3 ≤ 0.5.0

Public PoCMemory Safety
Published
01 January 2026
Modified
23 February 2026
CVSS Score v4 4.8
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
EPSS Score 0.0018 8th percentile
Risk Priority 25 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-15413 is a medium-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Wasm3 Project Wasm3. Its CVSS base score is 4.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-15413 is a memory corruption vulnerability (CWE-119, CWE-787) affecting wasm3 versions up to 0.5.0, specifically in the op_SetSlot_i32 and op_CallIndirect functions within the m3_exec.h file. Manipulation of these functions can lead to improper memory operations, such as out-of-bounds writes. The issue has a CVSS v3.1 base score of 5.3 (AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L), indicating medium severity with low confidentiality, integrity, and availability impacts.

The vulnerability requires local access (AV:L) with low privileges (PR:L), low attack complexity (AC:L), and no user interaction (UI:N). An attacker with local access could exploit it to cause memory corruption, potentially leading to limited disruption or data tampering as per the low impact scores. The exploit is public and available for use.

Advisories reference the wasm3 GitHub repository and issues #543 and #547, along with VulDB entries (ctiid.339334 and id.339334), but note no patches or fixes due to the project lacking an active maintainer. Security practitioners should avoid using affected wasm3 versions or isolate them in sandboxed environments.

Notably, the public exploit availability increases risk for deployments relying on this WebAssembly runtime, with no ongoing maintenance to address the issue.

EU & UK References

Vulnerability Data

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…

more

used. Unfortunately, the project has no active maintainer at the moment.

CWE(s)
CWE-119CWE-787

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-6272Same product: Wasm3 Project Wasm3
CVE-2024-8534Shared CWE-119, CWE-787
CVE-2023-28391Shared CWE-119, CWE-787
CVE-2023-38084Shared CWE-119, CWE-787
CVE-2023-31247Shared CWE-119, CWE-787
CVE-2024-11544Shared CWE-119, CWE-787
CVE-2023-21633Shared CWE-119, CWE-787
CVE-2023-28545Shared CWE-119, CWE-787
CVE-2024-23356Shared CWE-119, CWE-787
CVE-2024-0429Shared CWE-119, CWE-787

Affected Assets

wasm3 project
wasm3
≤ 0.5.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V17.3.2

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require memory-safe design and coding that structurally avoids buffer-boundary violations.

SI-10 Information Input Validation partial match

Input validation directly enforces bounds checking that stops out-of-bounds reads/writes from being introduced or reached.

SI-16 Memory Protection partial match

Memory protection restricts exploitation impact of buffer overflows without eliminating the underlying coding flaw.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices (bounds checking, safe APIs, reviews) directly prevent this class of flaw.

ID.RA-01 partial match
prevents

Vulnerability scanning and code analysis directly surface buffer-boundary flaws.

ID.RA-08 partial match
prevents

Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.

PR.AT-02 partial match
prevents

Developer training on secure coding reduces introduction of memory-buffer errors.

PR.PS-02 partial match
prevents

Patching replaces vulnerable code containing buffer-boundary defects.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches out-of-bounds accesses before release, covering most instances of the weakness.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates memory-safety practices that directly prevent buffer-boundary violations.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify memory-safety rules, but do not prescribe implementation details.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture and engineering principles include memory-safe design patterns that mitigate buffer overflows.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid unsafe buffer operations, directly eliminating CWE-119.

A.8.32 Change management partial match
prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References