# CVE-2025-71470: MicroQuickJS before commit 99eed3f Out-of-Bounds Read in build_backtrace

> Crafted JavaScript calling a non-function value crashes the MicroQuickJS engine via an out-of-bounds read; embedders running untrusted scripts should care.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 15 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-72q4-34j8-jv5x

## What is CVE-2025-71470?

CVE-2025-71470 is a medium-severity memory corruption vulnerability in bellard mquickjs, published on 15 Nov 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

MicroQuickJS (mquickjs) before commit 99eed3f contains an out-of-bounds read vulnerability because JS_Call() raises exceptions during frame setup without updating ctx->sp and ctx->fp. Attackers can supply JavaScript that calls a non-function value, causing build_backtrace() to walk stale frame pointers and crash the engine for denial of service.

Weakness: CWE-125 (Out-of-bounds Read)

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

An affected version is exposed as installed. No special setting or call is needed.


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

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

## Is CVE-2025-71470 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-71470 is a medium-severity memory corruption vulnerability in bellard mquickjs, published on 15 Nov 2026. It can only be exploited from the same machine or local network, 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-71470 exists.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected product: bellard mquickjs. 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-71470/ (Markdown: https://insights.sbomify.com/CVE-2025-71470/index.md)
```

## Sources

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

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