Findings

CVE-2025-15413

A vulnerability was detected in wasm3 up to 0.5.0.

Published Jan 1, 2026 · updated Oct 14, 2026 · wasm3 project wasm3

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.

Timeline

Detection, updates, and resolution for this record.

  1. Jan 1, 2026 · NIST NVD

    Detected

    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.

  2. Oct 14, 2026 · NIST NVD

    Updated

    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.

Affected

  • cpe wasm3 project/wasm3version unspecified

Sources

  • CVE.orgCVE-2025-15413

    Official CVE identifier

    cve.org
  • FIRST EPSSCVE-2025-15413

    30-day exploitation probability 0.2%

    first.org
  • NIST NVDCVE-2025-15413

    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. Unfortun

    nvd.nist.gov

References