{"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-92937 exists.","fix":"Upgrade vm2 to 3.11.7 or later.","what":"CVE-2026-92937 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-92937 and fix it if it is affected.\n\nWhat it is: CVE-2026-92937 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-92937 exists.\n\nAffected packages and fixed versions:\n- vm2 (npm): affected from 3.11.6; fixed in 3.11.7\n- vm2 (npm): affected from 3.11.6; 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-92937/ (Markdown: https://insights.sbomify.com/CVE-2026-92937/index.md)","id":"CVE-2026-92937","markdown":"https://insights.sbomify.com/CVE-2026-92937/index.md","name":"CVE-2026-92937","record":{"aliases":["CLEANSTART-2026-UO50229","ECHO-334d-48a7-6e03","GHSA-647f-g98j-qq25","MINI-h654-8g2r-hmwf","ROOT-APP-NPM-CVE-2026-92937"],"analysis":{"component_type":"library","fix_type":"upgrade","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 Node.js process by exploiting incomplete sanitization of Promise rejection handlers.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":10,"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:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"vm2 3.11.6 is vulnerable to a sandbox escape leading to remote code execution in the host Node.js process. The fix for GHSA-m283-3h24-438v is incomplete: the bridge gate at lib/bridge.js:1624 identity-checks only the direct call target when deciding whether to rebuild/sanitise a rejected host Promise value. Registering the rejection handler through Function.prototype.call or .apply indirection (e.g., p.then.call(p, undefined, cb)) makes the intercepted target host Function.prototype.call, so the sanitiser never runs and the raw host error reaches sandbox code with its own properties intact. If an embedder exposes a host-realm Promise to the sandbox (an async host function bridged via the sandbox option, or a NodeVM external module's async method) and that Promise rejects with an Error carrying a non-primitive own property referencing a host object (for example err.detail = process), untrusted code in the sandbox obtains a fully functional proxy to that host object and can execute arbitrary commands with the privileges of the host process (e.g., e.detail.mainModule.require('child_process').execSync(...)). The direct p.then(undefined, cb), bind, and Reflect.apply forms are correctly sanitised. Fixed in vm2 3.11.7.","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.11.6 Remote Code Execution via Promise call/apply","id":"CVE-2026-92937","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"vm2 3.11.3 through 3.11.6 Remote Code Execution via node:sqlite","id":"CVE-2026-92938"},"packages":[{"ecosystem":"npm","fixed":["3.11.7"],"introduced":["3.11.6"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-647f-g98j-qq25"},{"ecosystem":"npm","fixed":["3.11.7"],"introduced":["3.11.6"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-647f-g98j-qq25"}],"prev":{"headline":"vm2 3.11.0 before 3.11.7 Information Disclosure via Error Stack","id":"CVE-2026-92936"},"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-18","vendors":["patriksimek"]},"summary":"Attackers can escape the vm2 sandbox to execute arbitrary code on the host Node.js process by exploiting incomplete sanitization of Promise rejection handlers.","url":"https://insights.sbomify.com/CVE-2026-92937/"}