Vulnerabilities (CVE)

Filtered by vendor Quickjs-ng Subscribe
Filtered by product Quickjs
Total 5 CVE
CVE Vendors Products Updated CVSS v2 CVSS v3
CVE-2026-0822 1 Quickjs-ng 1 Quickjs 2026-01-22 7.5 HIGH 6.3 MEDIUM
A vulnerability was identified in quickjs-ng quickjs up to 0.11.0. This issue affects the function js_typed_array_sort of the file quickjs.c. The manipulation leads to heap-based buffer overflow. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. The identifier of the patch is 53eefbcd695165a3bd8c584813b472cb4a69fbf5. To fix this issue, it is recommended to deploy a patch.
CVE-2026-0821 1 Quickjs-ng 1 Quickjs 2026-01-15 7.5 HIGH 7.3 HIGH
A vulnerability was determined in quickjs-ng quickjs up to 0.11.0. This vulnerability affects the function js_typed_array_constructor of the file quickjs.c. Executing a manipulation can lead to heap-based buffer overflow. The attack may be launched remotely. The exploit has been publicly disclosed and may be utilized. This patch is called c5d80831e51e48a83eab16ea867be87f091783c5. A patch should be applied to remediate this issue.
CVE-2025-46687 2 Bellard, Quickjs-ng 2 Quickjs, Quickjs 2026-01-14 N/A 5.6 MEDIUM
quickjs-ng through 0.9.0 has a missing length check in JS_ReadString for a string, leading to a heap-based buffer overflow. QuickJS before 2025-04-26 is also affected.
CVE-2025-46688 2 Quickjs-ng, Quickjs Project 2 Quickjs, Quickjs 2025-05-30 N/A 5.6 MEDIUM
quickjs-ng through 0.9.0 has an incorrect size calculation in JS_ReadBigInt for a BigInt, leading to a heap-based buffer overflow. QuickJS before 2025-04-26 is also affected.
CVE-2024-13903 1 Quickjs-ng 1 Quickjs 2025-03-24 5.0 MEDIUM 4.3 MEDIUM
A vulnerability was found in quickjs-ng QuickJS up to 0.8.0. It has been declared as problematic. Affected by this vulnerability is the function JS_GetRuntime of the file quickjs.c of the component qjs. The manipulation leads to stack-based buffer overflow. The attack can be launched remotely. Upgrading to version 0.9.0 is able to address this issue. The patch is named 99c02eb45170775a9a679c32b45dd4000ea67aff. It is recommended to upgrade the affected component.