{"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-92944 exists.","fix":"Upgrade vm2 to 3.11.7 or later.","what":"CVE-2026-92944 is a critical code injection 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-92944 and fix it if it is affected.\n\nWhat it is: CVE-2026-92944 is a critical code injection 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-92944 exists.\n\nAffected packages and fixed versions:\n- vm2 (npm): affected from 3.10.2; fixed in 3.11.7\n- vm2 (npm): affected from 3.10.2; fixed in 3.11.7\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-92944/ (Markdown: https://insights.sbomify.com/CVE-2026-92944/index.md)","id":"CVE-2026-92944","markdown":"https://insights.sbomify.com/CVE-2026-92944/index.md","name":"CVE-2026-92944","record":{"aliases":["CLEANSTART-2026-WY20719","ECHO-89d0-4de4-3380","GHSA-27g9-p43v-cw3v","MINI-6vxp-r3ww-2h52","ROOT-APP-NPM-CVE-2026-92944"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js sandbox library","requires_auth":"none","summary":"Attackers can escape the vm2 sandbox to execute arbitrary code on the host system by exploiting a Promise protector bypass in Node.js.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"vm2 versions 3.10.2 through 3.11.6 contain a sandbox escape vulnerability on Node.js 26 where Promise.prototype.finally() bypasses vm2's wrapper protections due to a stale PromiseThenLookupChain protector in V8 14.6. Attackers can exploit this by creating an async function that returns a Promise with an attacker-controlled constructor Symbol.species, allowing them to reach the host Function constructor and process object for arbitrary code execution.","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.2 through 3.11.6 Sandbox Escape via Promise Protector","id":"CVE-2026-92944","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"vm2 before 3.11.7 Module Allowlist Bypass via Prefix Matching","id":"CVE-2026-92945"},"packages":[{"ecosystem":"npm","fixed":["3.11.7"],"introduced":["3.10.2"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-27g9-p43v-cw3v"},{"ecosystem":"npm","fixed":["3.11.7"],"introduced":["3.10.2"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-27g9-p43v-cw3v"}],"prev":{"headline":"Improper validation of certificate with host mismatch in AWS IoT Device SDK for Python","id":"CVE-2026-92943"},"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":"total"},"state":"PUBLISHED","updated":"2026-09-19","vendors":["patriksimek"]},"summary":"Attackers can escape the vm2 sandbox to execute arbitrary code on the host system by exploiting a Promise protector bypass in Node.js.","url":"https://insights.sbomify.com/CVE-2026-92944/"}