{"answers":{"affected":"2 open source packages ship an affected version, including vm2.","exploited":"There is no known exploitation of CVE-2026-47686 in the wild and no public exploit code.","fix":"Upgrade vm2 to 3.11.6 or later.","what":"CVE-2026-47686 is a critical code injection vulnerability in patriksimek vm2, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47686 and fix it if it is affected.\n\nWhat it is: CVE-2026-47686 is a critical code injection vulnerability in patriksimek vm2, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-47686 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- vm2 (npm): affected all versions; fixed in 3.11.6\n- vm2 (npm): affected all versions; fixed in 3.11.6\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-47686/ (Markdown: https://insights.sbomify.com/CVE-2026-47686/index.md)","id":"CVE-2026-47686","markdown":"https://insights.sbomify.com/CVE-2026-47686/index.md","name":"CVE-2026-47686","record":{"aliases":["CLEANSTART-2026-PD83197","ECHO-728a-4ca3-07f3","GHSA-m283-3h24-438v","MINI-qhpq-vwxw-56cv","ROOT-APP-NPM-CVE-2026-47686"],"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":"low_privilege","summary":"Attackers can escape the vm2 sandbox and execute arbitrary host commands by exploiting unsanitized Error.cause properties in exception handling.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.6, handleException() in lib/setup-sandbox.js sanitizes SuppressedError.error, SuppressedError.suppressed, and AggregateError.errors but does not sanitize Error.cause, allowing sandbox code to obtain a powerful host object such as process from an embedder-exposed host function that throws an error with that object as its cause and then execute arbitrary host commands. This issue is fixed in version 3.11.6.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"vm2: Missing Error.cause Sanitization Enables VM2 Sandbox Escape to RCE","id":"CVE-2026-47686","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":"FOGProject has stored XSS via unescaped option label in selectForm() accessible from unauthenticated inventory endpoint","id":"CVE-2026-47687"},"packages":[{"ecosystem":"npm","fixed":["3.11.6"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-m283-3h24-438v"},{"ecosystem":"npm","fixed":["3.11.6"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-m283-3h24-438v"}],"prev":{"headline":"FOGProject has stored XSS via unauthenticated inventory service renders unescaped in Host Management page","id":"CVE-2026-47685"},"products":["vm2"],"published":"2026-08-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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-19","vendors":["patriksimek"]},"summary":"Attackers can escape the vm2 sandbox and execute arbitrary host commands by exploiting unsanitized Error.cause properties in exception handling.","url":"https://insights.sbomify.com/CVE-2026-47686/"}