# CVE-2025-3122: WebAssembly wabt binary-reader-interp.cc BeginFunctionBody null pointer dereference

> A remote attacker can cause a denial of service in the WebAssembly wabt library via a null pointer dereference in the binary reader interpreter.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 2 Apr 2025
- **Updated:** 3 Apr 2025
- **Also known as:** DEBIAN-CVE-2025-3122, GHSA-8cmg-37qm-wxhr, PYSEC-2025-229, UBUNTU-CVE-2025-3122

## What is CVE-2025-3122?

CVE-2025-3122 is a low-severity vulnerability in WebAssembly wabt, published on 2 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability classified as problematic was found in WebAssembly wabt 1.0.36. Affected by this vulnerability is the function BinaryReaderInterp::BeginFunctionBody of the file src/interp/binary-reader-interp.cc. The manipulation leads to null pointer dereference. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

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

1 open source package ship an affected version, including wabt-bin. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `wabt-bin` | PyPI | All versions to 1.0.36 | None |

Products: Webassembly Webassembly Binary Toolkit.

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

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

## Is CVE-2025-3122 being exploited?

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

## Other vulnerabilities in WebAssembly wabt

- [CVE-2023-31670](https://insights.sbomify.com/CVE-2023-31670/): Denial of service in n/a (high 7.5)
- [CVE-2023-46331](https://insights.sbomify.com/CVE-2023-46331/): Memory corruption in n/a (medium 5.5)
- [CVE-2023-46332](https://insights.sbomify.com/CVE-2023-46332/): Memory corruption in n/a (medium 5.5)
- [CVE-2023-31669](https://insights.sbomify.com/CVE-2023-31669/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3122 is a low-severity vulnerability in WebAssembly wabt, published on 2 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3122 exists.

Affected packages and fixed versions:
- wabt-bin (PyPI): affected all versions up to 1.0.36; no fix listed

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-3122/ (Markdown: https://insights.sbomify.com/CVE-2025-3122/index.md)
```

## Sources

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

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