# CVE-2025-62492: Heap out-of-bounds read in js_typed_array_indexOf in QuickJS

> An attacker can trigger a heap out-of-bounds read in QuickJS via TypedArray.indexOf, potentially disclosing adjacent memory contents.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:P/VC:H/VI:L/VA:L/SC:H/SI:L/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Oct 2025
- **Updated:** 16 Oct 2025
- **Also known as:** DEBIAN-CVE-2025-62492, GHSA-7x74-j54q-cmv6, UBUNTU-CVE-2025-62492

## What is CVE-2025-62492?

CVE-2025-62492 is a medium-severity vulnerability in QuickJS, published on 16 Oct 2025. 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

A vulnerability stemming from floating-point arithmetic precision errors exists in the QuickJS engine's implementation of TypedArray.prototype.indexOf() when a negative fromIndex argument is supplied.

  *  The fromIndex argument (read as a double variable, $d$) is used to calculate the starting position for the search.

  *  If d is negative, the index is calculated relative to the end of the array by adding the array's length (len) to d:

$$d_{new} = d + \text{len}$$

  *  Due to the inherent limitations of floating-point arithmetic, if the negative value $d$ is extremely small (e.g., $-1 \times 10^{-20}$), the addition $d + \text{len}$ can result in a loss of precision, yielding an outcome that is exactly equal to $\text{len}$.

  *  The result is then converted to an integer index $k$: $k = \text{len}$.

  *  The search function proceeds to read array elements starting from index $k$. Since valid indices are $0$ to $\text{len}-1$, starting the read at index $\text{len}$ is one element past the end of the array.

This allows an attacker to cause an Out-of-Bounds Read of one element immediately following the buffer. While the scope of this read is small (one element), it can potentially lead to Information Disclosure of adjacent memory contents, depending on the execution environment.

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

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

It affects 1 product.


Products: Quickjs Project Quickjs.

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

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

## Is CVE-2025-62492 being exploited?

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

## Other vulnerabilities in QuickJS

- [CVE-2025-62490](https://insights.sbomify.com/CVE-2025-62490/): Use-after-free in js_print_object in QuickJS (high 8.8)
- [CVE-2025-62491](https://insights.sbomify.com/CVE-2025-62491/): Use-after-free in js_std_promise_rejection_check in QuickJS (high 8.8)
- [CVE-2025-69654](https://insights.sbomify.com/CVE-2025-69654/): Denial of service in n/a (high 7.5)
- [CVE-2023-48183](https://insights.sbomify.com/CVE-2023-48183/): Null dereference in n/a (high 7.5)
- [CVE-2023-31922](https://insights.sbomify.com/CVE-2023-31922/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-62492 is a medium-severity vulnerability in QuickJS, published on 16 Oct 2025. 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-62492 exists.

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

## Sources

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

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