{"answers":{"affected":"2 open source packages ship an affected version, including vm2.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92954 exists.","fix":"Upgrade vm2 to 3.11.8 or later.","what":"CVE-2026-92954 is a critical denial of service vulnerability in patriksimek vm2, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-92954 and fix it if it is affected.\n\nWhat it is: CVE-2026-92954 is a critical denial of service vulnerability in patriksimek vm2, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92954 exists.\n\nAffected packages and fixed versions:\n- vm2 (npm): affected from 3.10.0; fixed in 3.11.8\n- vm2 (npm): affected from 3.10.0; fixed in 3.11.8\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-2026-92954/ (Markdown: https://insights.sbomify.com/CVE-2026-92954/index.md)","id":"CVE-2026-92954","markdown":"https://insights.sbomify.com/CVE-2026-92954/index.md","name":"CVE-2026-92954","record":{"aliases":["CLEANSTART-2026-IT25891","ECHO-0f0b-25d6-437d","GHSA-gjq8-xm47-88rc","MINI-2vxr-w6pw-qfv7","ROOT-APP-NPM-CVE-2026-92954"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js sandbox library","requires_auth":"none","summary":"An attacker can crash the host Node.js process by ignoring rejected Promises returned from host functions within the vm2 sandbox.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.2,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H","version":"4.0"},"cwes":[{"id":"CWE-248","name":"Uncaught Exception"}],"description":"vm2 is a sandbox library for running untrusted JavaScript in Node.js. In versions \u003e= 3.10.0 and \u003c= 3.11.7, Promises returned from the host realm into the sandbox are not marked as handled at the bridge boundary; only Promises created inside the sandbox are wrapped with a rejection-swallowing handler (lib/setup-sandbox.js), and the bridge only installs host-side rejection sanitizers when sandbox code calls .then/.catch/.finally. As a result, code running in the sandbox can invoke a host function that returns a rejected Promise (for example events.once() exposed via the NodeVM events builtin, or any embedder-provided Promise-returning API) and simply ignore the return value, leaving the host Promise unhandled so that Node.js's default unhandled-rejection behavior terminates the host process. This is an incomplete fix of GHSA-hw58-p9xv-2mjh. The issue is fixed in version 3.11.8.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"vm2 3.10.0 through 3.11.7 Denial of Service via Host Promise","id":"CVE-2026-92954","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"vm2 before 3.11.8 Sandbox Escape via NodeVM","id":"CVE-2026-92955"},"packages":[{"ecosystem":"npm","fixed":["3.11.8"],"introduced":["3.10.0"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-gjq8-xm47-88rc"},{"ecosystem":"npm","fixed":["3.11.8"],"introduced":["3.10.0"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-gjq8-xm47-88rc"}],"prev":{"headline":"vm2 3.11.0 through 3.11.7 Prototype Pollution via TypedArray","id":"CVE-2026-92953"},"products":["vm2"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-26","vendors":["patriksimek"]},"summary":"An attacker can crash the host Node.js process by ignoring rejected Promises returned from host functions within the vm2 sandbox.","url":"https://insights.sbomify.com/CVE-2026-92954/"}