In quickjs, in js_print_object, when printing an array, the function first fetches the array length and then loops over it. The issue is, printing a value is not side-effect free. An attacker-defined callback could run during js_print_value, during which the array could get resized and len1 become out of bounds. This results in a use-after-free.A second instance occurs in the same function during printing of a map or set objects. The code iterates over ms->records list, but once again, elements could be removed from the list during js_print_value call.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 1
- First seenCVSS 8.8 · quickjs_projectNVD modified 2026-10-19 16:10
Affected (CPE criteria) 1
cpe:2.3:a:quickjs_project:quickjs:*:*:*:*:*:*:*:*
References 2
- https://bellard.org/quickjs/Changelog Release Notes
- https://issuetracker.google.com/434196651 Exploit, Issue Tracking