Skip to content
CVE Alert: CVE-2026-120438 – quickjs-ng – QuickJS

CVE Alert: CVE-2026-120438 – quickjs-ng – QuickJS

Redpacketsecurity •admin • November 2, 2026

QuickJS-NG before 0.16.0 contains an integer overflow in js_proxy_get_own_property_names() in quickjs.c that causes a heap buffer overflow on 32-bit hosts. Attackers running JavaScript can return a large array-like object from a Proxy ownKeys trap to wrap the allocation size, causing crashes or potential code execution.

**Risk verdict:** High impact where untrusted JavaScript runs on an affected 32-bit host; exploitation status and prevalence are unconfirmed because KEV, SSVC, PoC and EPSS data were not provided.

**Why this matters:** Successful exploitation could compromise the confidentiality, integrity and availability of the process running the engine. Realistic attacker goals include crashing a service or gaining code execution in an application that processes attacker-controlled scripts. The practical risk depends heavily on whether such scripts can reach the engine.

**Most likely attack path:** An attacker needs low-level local access or an existing route to submit JavaScript to the vulnerable process; no additional user action is indicated. The impact is scoped to that process’s security boundary, so lateral movement is not inherent, though an attacker may use the compromised process’s permissions to access local resources.

**Who is most exposed:** Prioritise 32-bit systems embedding the engine in scriptable applications, automation, plugins, or services that process untrusted content. Exposure is lower where JavaScript is trusted and tightly controlled.

Identify embedded engine versions and 32-bit runtime deployments.

Review script inputs, including plugin, job and request sources.

Monitor crashes or abnormal memory errors during property enumeration.

Alert on unexpected child processes or file and network activity from engine-hosting applications.

Mitigation and prioritisation

Upgrade affected deployments to the fixed release; inventory embedded copies, not just standalone packages.

Until upgraded, block untrusted scripts and restrict script execution to trusted inputs.

Apply least privilege and isolate script-running processes from sensitive files and credentials.

Test integrations and stage rollout; confirm the deployed runtime is actually updated.

Obtain exploitation and EPSS status before final ranking; raise urgency if active exploitation is confirmed.

A considerable amount of time and effort goes into maintaining this website, creating backend automation and creating new features and content for you to make actionable intelligence decisions. Everyone that supports the site helps enable new functionality.

If you like the site, please support us on Patreon or Buy Me A Coffee using the buttons below.