CVE-2026-1145VulnerabilityPublished 19 Jan 2026Updated 25 Feb 2026

CVE-2026-1145: quickjs · Heap-based Buffer Overflow

Affects quickjsSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
quickjs-ngquickjs	Affected =0.1 =0.2 =0.3 =0.4 =0.5 =0.6 =0.7 =0.8 =0.9 =0.10 =0.11.0	Fixed in–
GitHubquickjs-ng/quickjs`pkg:github/quickjs-ng/quickjs`Other threats	Affected =0.1 =0.2 =0.3 =0.4 =0.5 =0.6 =0.7 =0.8 =0.9 =0.10 =0.11.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should immediately update quickjs-ng quickjs to versions beyond 0.11.0 that include the patch identified by commit 53aebe66170d545bb6265906fe4324e4477de8b4. Where updating is not immediately feasible, implement runtime mitigations such as enabling memory safety features, sandboxing the JavaScript engine execution environment, and applying strict input validation to prevent processing of untrusted or malformed JavaScript code. Employ network-level protections to limit exposure of services embedding quickjs-ng to untrusted sources. Security teams should monitor for indicators of compromise related to this vulnerability and apply intrusion detection signatures where available. Regularly audit embedded devices and applications for the presence of vulnerable quickjs-ng versions and prioritize patching accordingly.

Description

A flaw has been found in quickjs-ng quickjs up to 0.11.0. Affected by this vulnerability is the function js_typed_array_constructor_ta of the file quickjs.c. This manipulation causes heap-based buffer overflow. The attack is possible to be carried out remotely. The exploit has been published and may be used. Patch name: 53aebe66170d545bb6265906fe4324e4477de8b4. It is suggested to install a patch to address this issue.

Impact

The heap-based buffer overflow in quickjs-ng quickjs can lead to memory corruption, which attackers may leverage to execute arbitrary code remotely or cause application crashes resulting in denial of service. For organizations, this could mean compromise of devices or applications that embed quickjs-ng, potentially leading to unauthorized control, data breaches, or service disruptions. Given quickjs-ng's use in embedded and IoT devices, exploitation could affect critical infrastructure, consumer electronics, or industrial control systems. The requirement for user interaction limits automated widespread exploitation but targeted attacks remain feasible. The medium CVSS score reflects moderate risk; however, the availability of a public exploit increases the urgency for remediation. Organizations relying on quickjs-ng in their software stack must consider the risk of lateral movement or persistent compromise if exploited.

Summary

CVE-2026-1145 identifies a heap-based buffer overflow vulnerability in the quickjs-ng quickjs JavaScript engine, specifically in the function js_typed_array_constructor_ta located in quickjs.c. This function improperly handles typed array construction, leading to a heap overflow condition when processing maliciously crafted inputs. The vulnerability affects all versions up to and including 0.11.0. The flaw can be exploited remotely without requiring authentication or elevated privileges, but user interaction is necessary to trigger the vulnerability, such as processing malicious JavaScript code. The overflow can corrupt heap memory, potentially allowing attackers to execute arbitrary code, crash the application, or cause denial of service. The vulnerability has been assigned a CVSS 4.0 score of 5.3, reflecting medium severity due to the combination of remote exploitability, user interaction requirement, and limited impact on confidentiality, integrity, and availability. A patch identified by commit 53aebe66170d545bb6265906fe4324e4477de8b4 has been released to address this issue. No confirmed exploits are currently observed in the wild, but proof-of-concept code is publicly available, increasing the risk of exploitation. Quickjs-ng quickjs is commonly embedded in IoT devices, embedded systems, and applications requiring lightweight JavaScript engines, making this vulnerability relevant to those environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Mar 2026, 01:17 UTC

Technical details

References

Community reviews

Related threats