CVE-2025-62495: Type confusion in string addition in QuickJS
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.46% (FIRST EPSS).
- Someone on the same network segment can trigger it. A low-privileged account is enough. Special conditions such as timing or configuration are required.
- Fixed version: QuickJS QuickJS 2025-09-13.
Low priority for now. Upgrade to QuickJS QuickJS 2025-09-13 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An integer overflow vulnerability exists in the QuickJS regular expression engine (libregexp) due to an inconsistent representation of the bytecode buffer size. * The regular expression bytecode is stored in a DynBuf structure, which correctly uses a $\text{size}\_\text{t}$ (an unsigned type, typically 64-bit) for its size member. * However, several functions, such as re_emit_op_u32 and other internal parsing routines, incorrectly cast or store this DynBuf $\text{size}\_\text{t}$ value into a signed int (typically 32-bit). * When a large or complex regular expression (such as those generated by a recursive pattern in a Proof-of-Concept) causes the bytecode size to exceed $2^{31}$ bytes (the maximum positive value for a signed 32-bit integer), the size value wraps around, resulting in a negative integer when stored in the int variable (Integer Overflow). * This negative value is subsequently used in offset calculations. For example, within functions like re_parse_disjunction, the negative size is used to compute an offset (pos) for patching a jump instruction. * This negative offset is then incorrectly added to the buffer pointer (s->byte\_code.buf + pos), leading to an out-of-bounds write on the first line of the snippet below: put_u32(s->byte_code.buf + pos, len);
- Published
- Oct 16, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-191
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Google
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| quickjs project | quickjs | cpe:2.3:a:quickjs_project:quickjs |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Google). Independent of NVD's CPE analysis and usually ahead of it.
QuickJS QuickJS
- 2025-04-26 and later · before 2025-09-13affected · date
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- quickjs project quickjsbefore 2025-09-13
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | quickjs | from 0 | — |
Same product
quickjs project: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-62491Use-after-free in js_std_promise_rejection_check in QuickJS35Monitor
- CVE-2025-62490Use-after-free in js_print_object in QuickJS35Monitor
- CVE-2025-69654A crafted JavaScript input executed with the QuickJS release 2025-09-13, fixed in commit fcd33c1afa7b3028531f53cd1190a3877454f6b3…30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-62493Oct 16, 2025 · Heap out-of-bounds read in js_bigint_to_string1 in QuickJS23Monitor
- ← EarlierCVE-2025-62494Oct 16, 2025 · Type confusion in string addition in QuickJS28Monitor
- Later →CVE-2025-62496Oct 16, 2025 · Integer overflow in js_bigint_from_string in QuickJS28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| QuickJS QuickJS | 2025-09-13 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Google Big Sleepfinder
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- A low-privileged account is enough.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-191 · Integer Underflow (Wrap or Wraparound)CVSS vector
CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.