# CVE-2026-120439: QuickJS-NG before 0.16.0 Heap Buffer Overflow via TypedArray.prototype.sort


- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 2 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-120439, GHSA-9wv5-5cgr-grj6, GHSA-xffc-9827-rpvc, UBUNTU-CVE-2026-120439

## What is CVE-2026-120439?

CVE-2026-120439 is a high-severity vulnerability in QuickJS-NG, published on 2 Nov 2026. 

### Official description

QuickJS-NG before 0.16.0 contains an integer overflow in js_typed_array_sort() in quickjs.c that allows attackers to cause a heap buffer overflow on 32-bit hosts. Attackers who can run JavaScript can call TypedArray.prototype.sort with a comparator on a typed array near 2^30 elements, wrapping the allocation size and writing indices past the buffer to crash or potentially execute code.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2026-120439?


## How do I fix CVE-2026-120439?

Upgrade to a fixed version.

## Is CVE-2026-120439 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120439 and fix it if it is affected.

What it is: CVE-2026-120439 is a high-severity vulnerability in QuickJS-NG, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120439 exists.

Affected product: QuickJS-NG. 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-2026-120439/ (Markdown: https://insights.sbomify.com/CVE-2026-120439/index.md)
```

## Sources

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

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