# CVE-2025-15412: WebAssembly wabt wasm-decompile VarName out-of-bounds

> An out-of-bounds read in wabt's wasm-decompile tool allows local attackers to cause crashes or leak memory contents.

- **Severity:** Medium 4.8 (`CVSS: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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jan 2026
- **Updated:** 23 Feb 2026
- **Also known as:** DEBIAN-CVE-2025-15412, GHSA-q9fv-9fr9-69p3, UBUNTU-CVE-2025-15412

## What is CVE-2025-15412?

CVE-2025-15412 is a medium-severity memory corruption vulnerability in WebAssembly wabt, published on 1 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A security vulnerability has been detected in WebAssembly wabt up to 1.0.39. This issue affects the function wabt::Decompiler::VarName of the file /src/repro/wabt/bin/wasm-decompile of the component wasm-decompile. Such manipulation leads to out-of-bounds read. Local access is required to approach this attack. The exploit has been disclosed publicly and may be used. Unfortunately, the project has no active maintainer at the moment. In a reply to the issue report somebody recommended to the researcher to provide a PR himself.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-15412?

It affects 1 product.


Products: Webassembly Wabt.

## How do I fix CVE-2025-15412?

No fix has been published for CVE-2025-15412 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-15412 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15412 exists.

## Other vulnerabilities in WebAssembly wabt

- [CVE-2022-43280](https://insights.sbomify.com/CVE-2022-43280/): Memory corruption in n/a (high 7.1)
- [CVE-2022-43282](https://insights.sbomify.com/CVE-2022-43282/): Memory corruption in n/a (high 7.1)
- [CVE-2023-27119](https://insights.sbomify.com/CVE-2023-27119/): Null dereference in n/a (medium 5.5)
- [CVE-2022-43283](https://insights.sbomify.com/CVE-2022-43283/): Denial of service in n/a (medium 5.5)
- [CVE-2025-2368](https://insights.sbomify.com/CVE-2025-2368/): WebAssembly wabt Malformed File binary-reader-interp.cc OnExport heap-based overflow (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15412 and fix it if it is affected.

What it is: CVE-2025-15412 is a medium-severity memory corruption vulnerability in WebAssembly wabt, published on 1 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15412 exists.

Affected product: WebAssembly wabt. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15412/ (Markdown: https://insights.sbomify.com/CVE-2025-15412/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15412
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15412
- OSV: https://osv.dev/vulnerability/CVE-2025-15412

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15412/
Summaries are generated and may contain mistakes; the official description above is the record.