Finding and attribution
An off-by-one digit calculation in BigInt string conversion can read past the allocated BigInt structure. The QuickJS upstream changelog lists release 2025-09-13 as the next release; no exploit claim is made.
Product: QuickJS. AI system: Google Big Sleep. Team / organization: Google and QuickJS.
CVE identifiers: CVE-2025-62493.
AI and human contribution (source account): The Google-assigned CVE record credits Google Big Sleep as finder and references the individual Google Issue Tracker report (434193024). The sources do not specify human review steps.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The public Google-assigned CVE record attributes the finder and lists versions before 2025-09-13 as affected; no exploitation claim is made.
Remediation status: fix documented. Google CNA record identifies versions earlier than QuickJS 2025-09-13 as affected; the upstream changelog confirms that release date. The changelog itself only summarizes miscellaneous bug fixes, so no specific commit is identified here.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 16 Oct 2025. AI attribution dated 16 Oct 2025. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Medium · highest recorded score 5.9. Documented technical effects: data disclosure.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2025-62493: CVSS 4.0 · 5.9 (Medium) ·
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· Assessment scenarios: GENERAL. Google (CNA; CVE Program record) · checked 16 Nov 2026.
CVE-2025-62493: data disclosure.
Prerequisites / affected scope: CNA description: A vulnerability exists in the QuickJS engine's BigInt string conversion logic (js_bigint_to_string1) due to an incorrect calculation of the required number of digits, which in turn leads to reading memory past the allocated BigInt structure.
* The function determines the number of characters (n_digits) needed for the string representation by calculating:
$$ \\ \text{n\_digits} = (\text{n\_bits} + \text{log2\_radix} - 1) / \text{log2\_radix}$$
$$$$This formula is off-by-one in certain edge cases when calculating the necessary memory limbs. For instance, a 127-bit BigInt using radix 32 (where $\text{log2\_radix}=5$) is calculated to need $\text{n\_digits}=26$.
* The maximum number of bits actually stored is $\text{n\_bits}=127$, which requires only two 64-bit limbs ($\text{JS\_LIMB\_BITS}=64$).
* The conversion loop iterates $\text{n\_digits}=26$ times, attempting to read 5 bits in each iteration, totaling $26 \times 5 = 130$ bits.
* In the final iterations of the loop, the code attempts to read data that spans two limbs:
C
c = (r->tab[pos] >> shift) | (r->tab[pos + 1] << (JS_LIMB_BITS - shift));
* Since the BigInt was only allocated two limbs, the read operation for r->tab[pos + 1] becomes an Out-of-Bounds Read when pos points to the last valid limb (e.g., $pos=1$).
This vulnerability allows an attacker to cause the engine to read and process data from the memory immediately following the BigInt buffer. This can lead to Information Disclosure of sensitive data stored on the heap adjacent to the BigInt object..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: Google CNA record identifies versions earlier than QuickJS 2025-09-13 as affected; the upstream changelog confirms that release date. The changelog itself only summarizes miscellaneous bug fixes, so no specific commit is identified here.