# CVE-2025-6275: WebAssembly wabt binary-reader-interp.cc GetFuncOffset use after free

> A use-after-free flaw in the wabt library allows local attackers to potentially execute arbitrary code or cause a denial of service via crafted WebAssembly binaries.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/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:** 19 Jun 2025
- **Updated:** 23 Jun 2025
- **Also known as:** DEBIAN-CVE-2025-6275, GHSA-w5x9-mj5j-cp4g, UBUNTU-CVE-2025-6275

## What is CVE-2025-6275?

CVE-2025-6275 is a medium-severity use after free vulnerability in WebAssembly wabt, published on 19 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in WebAssembly wabt up to 1.0.37. It has been declared as problematic. Affected by this vulnerability is the function GetFuncOffset of the file src/interp/binary-reader-interp.cc. The manipulation leads to use after free. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. A similar issue reported during the same timeframe was disputed by the code maintainer because it might not affect "real world wasm programs". Therefore, this entry might get disputed as well in the future.

Weakness: CWE-416 (Use After Free), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Webassembly Wabt.

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

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

## Is CVE-2025-6275 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6275 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-6275 and fix it if it is affected.

What it is: CVE-2025-6275 is a medium-severity use after free vulnerability in WebAssembly wabt, published on 19 Jun 2025. 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-6275 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-6275/ (Markdown: https://insights.sbomify.com/CVE-2025-6275/index.md)
```

## Sources

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

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