{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62494 exists.","fix":"No fix has been published for CVE-2025-62494 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-62494 is a high-severity memory corruption vulnerability in QuickJS, published on 16 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-62494 and fix it if it is affected.\n\nWhat it is: CVE-2025-62494 is a high-severity memory corruption vulnerability in QuickJS, published on 16 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62494 exists.\n\nAffected product: QuickJS. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-62494/ (Markdown: https://insights.sbomify.com/CVE-2025-62494/index.md)","id":"CVE-2025-62494","markdown":"https://insights.sbomify.com/CVE-2025-62494/index.md","name":"CVE-2025-62494","record":{"aliases":["DEBIAN-CVE-2025-62494","GHSA-7gcv-76g2-94qm","UBUNTU-CVE-2025-62494"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"JavaScript engine","requires_auth":"low_privilege","summary":"Type confusion in QuickJS string addition allows attackers to trigger memory corruption and execute arbitrary code via crafted JavaScript.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Google","cpe":[{"product":"quickjs","vendor":"quickjs_project"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L","version":"4.0"},"cwes":[{"id":"CWE-704","name":"Incorrect Type Conversion or Cast"}],"description":"A type confusion vulnerability exists in the handling of the string addition (+) operation within the QuickJS engine.\n\n  *  The code first checks if the left-hand operand is a string.\n\n  *  It then attempts to convert the right-hand operand to a primitive value using JS_ToPrimitiveFree. This conversion can trigger a callback (e.g., toString or valueOf).\n\n  *  During this callback, an attacker can modify the type of the left-hand operand in memory, changing it from a string to a different type (e.g., an object or an array).\n\n  *  The code then proceeds to call JS_ConcatStringInPlace, which still treats the modified left-hand value as a string.\n\nThis mismatch between the assumed type (string) and the actual type allows an attacker to control the data structure being processed by the concatenation logic, resulting in a type confusion condition. This can lead to out-of-bounds memory access, potentially resulting in memory corruption and arbitrary code execution in the context of the QuickJS runtime.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Type confusion in string addition in QuickJS","id":"CVE-2025-62494","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Type confusion in string addition in QuickJS","id":"CVE-2025-62495"},"packages":[],"prev":{"headline":"Heap out-of-bounds read in js_bigint_to_string1 in QuickJS","id":"CVE-2025-62493"},"products":["QuickJS"],"published":"2025-10-16","related":[{"cvss_score":8.8,"headline":"Use-after-free in js_print_object in QuickJS","id":"CVE-2025-62490","kev_date_added":null,"published":"2025-10-16"},{"cvss_score":8.8,"headline":"Use-after-free in js_std_promise_rejection_check in QuickJS","id":"CVE-2025-62491","kev_date_added":null,"published":"2025-10-16"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2025-69654","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2023-48183","kev_date_added":null,"published":"2024-04-23"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2023-31922","kev_date_added":null,"published":"2023-05-12"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2020-22876","kev_date_added":null,"published":"2021-07-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-10-16","vendors":["QuickJS"]},"summary":"Type confusion in QuickJS string addition allows attackers to trigger memory corruption and execute arbitrary code via crafted JavaScript.","url":"https://insights.sbomify.com/CVE-2025-62494/"}