{"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-47210 exists.","fix":"Upgrade vm2 to 3.11.4 or later.","what":"CVE-2026-47210 is a critical code injection vulnerability in patriksimek vm2, published on 12 Jun 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-47210 and fix it if it is affected.\n\nWhat it is: CVE-2026-47210 is a critical code injection vulnerability in patriksimek vm2, published on 12 Jun 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-47210 exists.\n\nAffected packages and fixed versions:\n- vm2 (npm): affected all versions; fixed in 3.11.4\n- vm2 (npm): affected all versions; fixed in 3.11.4\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-47210/ (Markdown: https://insights.sbomify.com/CVE-2026-47210/index.md)","id":"CVE-2026-47210","markdown":"https://insights.sbomify.com/CVE-2026-47210/index.md","name":"CVE-2026-47210","record":{"aliases":["ECHO-a718-c1c0-dbe7","GHSA-6j2x-vhqr-qr7q","MINI-45h5-4vvj-h7x3","ROOT-APP-NPM-CVE-2026-47210"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Node.js sandbox library","requires_auth":"none","summary":"Attackers can escape the vm2 sandbox and execute arbitrary code on the host by exploiting a Promise species bypass in JSPI-enabled runtimes.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-913","name":"Improper Control of Dynamically-Managed Code Resources"}],"description":"vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, a sandbox escape vulnerability in vm2 allows arbitrary code execution in the host process when untrusted code is executed with async support on runtimes exposing WebAssembly JSPI (WebAssembly.promising / WebAssembly.Suspending). In the tested configuration, a JSPI-backed Promise can reach Promise.prototype.finally() in a way that bypasses the expected Promise-species hardening and exposes a host-originated rejection object to attacker-controlled species logic, breaking the sandbox boundary. This issue has been patched in version 3.11.4.","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 sandbox escape via JSPI-backed Promise `.finally()` species bypass","id":"CVE-2026-47210","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Ouroboros: Remote Code Execution via Untrusted Project-Directory .env","id":"CVE-2026-47211"},"packages":[{"ecosystem":"npm","fixed":["3.11.4"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-6j2x-vhqr-qr7q"},{"ecosystem":"npm","fixed":["3.11.4"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-6j2x-vhqr-qr7q"}],"prev":{"headline":"vm2: Bridge Proxy set trap ignores receiver parameter, enabling host object property injection via prototype chain","id":"CVE-2026-47209"},"products":["vm2"],"published":"2026-06-12","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-06-13","vendors":["patriksimek"]},"summary":"Attackers can escape the vm2 sandbox and execute arbitrary code on the host by exploiting a Promise species bypass in JSPI-enabled runtimes.","url":"https://insights.sbomify.com/CVE-2026-47210/"}