# 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-re...

Advisory record · `PYSEC-2025-229`

- **Identifiers:** `PYSEC-2025-229` · `CVE-2025-3122`
- **State:** Confirmed
- **Severity:** CVSS 2.3 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-404](https://cwe.mitre.org/data/definitions/404.html) · [CWE-476](https://cwe.mitre.org/data/definitions/476.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) · [Memory corruption](https://agentprime.io/advisories/tag/memory-corruption.md)
- **Published:** 2 Apr 2025
- **Updated:** 21 May 2026
- **Reviewed by a person:** No

Published by OSV at 2 Apr 2025, 22:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `wabt-bin` (PyPI): affected `<=1.0.36`; no fixed version yet

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 2.3 Low, CVSS 4.0: `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`, from CNA (VulDB)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0061, the 50th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of OSV, published 2 Apr 2025. New records show when each source confirmed them.

## Sources

- [OSV: PYSEC-2025-229](https://osv.dev/vulnerability/PYSEC-2025-229)
- <https://vuldb.com/?id.303013>
- <https://vuldb.com/?submit.525091>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/PYSEC-2025-229>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/PYSEC-2025-229/>. Everything for agents: <https://agentprime.io/llms.txt>.
