How severe is CVE-2025-69654?

CVE-2025-69654 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2025-69654 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-69654?

CVE-2025-69654 affects Quickjs Project Quickjs. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2025-69654?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-69654 have an EU (EUVD) identifier?

Yes. CVE-2025-69654 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-208350.

When was CVE-2025-69654 published?

CVE-2025-69654 was published on 2026-03-06 and last updated on 2026-06-17.

CVE-2025-69654

CVE-2025-69654 is a high-severity vulnerability in Quickjs Project Quickjs with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-400.

Key facts

Severity: High (CVSS 3.x base score 7.5)
EPSS exploit prediction: 0% (20th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-208350
Weakness: CWE-400
Affected product: Quickjs Project Quickjs
Published: 2026-03-06
Last modified: 2026-06-17

Description

A crafted JavaScript input executed with the QuickJS release 2025-09-13, fixed in commit fcd33c1afa7b3028531f53cd1190a3877454f6b3 (2025-12-11),`qjs` interpreter using the `-m` option and a low memory limit can cause an out-of-memory condition followed by an assertion failure in JS_FreeRuntime (list_empty(&rt->gc_obj_list)) during runtime cleanup. Although the engine reports an OOM error, it subsequently aborts with SIGABRT because the GC object list is not fully released. This results in a denial of service.

Frequently asked questions

What is CVE-2025-69654?: A crafted JavaScript input executed with the QuickJS release 2025-09-13, fixed in commit fcd33c1afa7b3028531f53cd1190a3877454f6b3 (2025-12-11),`qjs` interpreter using the `-m` option and a low memory limit can cause an out-of-memory condition followed by an assertion failure in JS_FreeRuntime (list_empty(&rt->gc_obj_list)) during runtime cleanup. Although the engine reports an OOM error, it subsequently aborts with SIGABRT because the GC object list is not fully released. This results in a denial of service.
How severe is CVE-2025-69654?: CVE-2025-69654 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2025-69654 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-69654?: CVE-2025-69654 affects Quickjs Project Quickjs. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-69654?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-69654 have an EU (EUVD) identifier?: Yes. CVE-2025-69654 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-208350.
When was CVE-2025-69654 published?: CVE-2025-69654 was published on 2026-03-06 and last updated on 2026-06-17.

References

https://github.com/bellard/quickjs/issues/468

Affected products (1)

cpe:2.3:a:quickjs_project:quickjs:*:*:*:*:*:*:*:*

More vulnerabilities in Quickjs Project Quickjs

CVE-2025-62496 — High (CVSS 8.8): A vulnerability exists in the QuickJS engine's BigInt string parsing logic (js_bigint_from_string) when attempting to…
CVE-2025-62495 — High (CVSS 8.8): An integer overflow vulnerability exists in the QuickJS regular expression engine (libregexp) due to an inconsistent…
CVE-2025-62494 — High (CVSS 8.8): A type confusion vulnerability exists in the handling of the string addition (+) operation within the QuickJS engine.…
CVE-2025-62491 — High (CVSS 8.8): A Use-After-Free (UAF) vulnerability exists in the QuickJS engine's standard library when iterating over the global…
CVE-2025-62490 — High (CVSS 8.8): In quickjs, in js_print_object, when printing an array, the function first fetches the array length and then loops over…
CVE-2023-48183 — High (CVSS 7.5): QuickJS before c4cdd61 has a build_for_in_iterator NULL pointer dereference because of an erroneous lexical scope of…

All CVEs affecting Quickjs Project Quickjs →

Other CWE-400 (Uncontrolled Resource Consumption) vulnerabilities

CVE-2026-46775 — Critical (CVSS 9.9): Vulnerability in Oracle REST Data Services (component: Core). Supported versions that are affected are 24.2.0-26.1.0.…
CVE-2025-61303 — Critical (CVSS 9.8): Hatching Triage Sandbox Windows 10 build 2004 (2025-08-14) and Windows 10 LTSC 2021(2025-08-14) contains a…
CVE-2025-43193 — Critical (CVSS 9.8): The issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.6, macOS Sonoma 14.7.7,…
CVE-2025-24269 — Critical (CVSS 9.8): The issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.4. An app may be able to…
CVE-2025-24264 — Critical (CVSS 9.8): The issue was addressed with improved memory handling. This issue is fixed in Safari 18.4, iOS 18.4 and iPadOS 18.4,…
CVE-2025-24260 — Critical (CVSS 9.8): The issue was addressed with improved memory handling. This issue is fixed in macOS Sequoia 15.4, macOS Sonoma 14.7.5,…

Browse all CWE-400 (Uncontrolled Resource Consumption) vulnerabilities →