{"answers":{"affected":"2 open source packages ship an affected version, including vm2. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-36067 exists.","fix":"Upgrade vm2 to 3.9.11 or later.","what":"CVE-2022-36067 is a critical code injection vulnerability in patriksimek vm2, published on 6 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-36067 and fix it if it is affected.\n\nWhat it is: CVE-2022-36067 is a critical code injection vulnerability in patriksimek vm2, published on 6 Sep 2022. 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-2022-36067 exists.\n\nAffected packages and fixed versions:\n- vm2 (npm): affected all versions; fixed in 3.9.11\n- vm2 (npm): affected all versions; fixed in 3.9.11\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-2022-36067/ (Markdown: https://insights.sbomify.com/CVE-2022-36067/index.md)","id":"CVE-2022-36067","markdown":"https://insights.sbomify.com/CVE-2022-36067/index.md","name":"CVE-2022-36067","record":{"aliases":["GHSA-mrgp-mrhc-5jrq","ROOT-APP-NPM-CVE-2022-36067"],"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 bypass sandbox protections in vm2 to execute arbitrary code on the host system.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vm2","vendor":"vm2_project"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-913","name":"Improper Control of Dynamically-Managed Code Resources"}],"description":"vm2 is a sandbox that can run untrusted code with whitelisted Node's built-in modules. In versions prior to version 3.9.11, a threat actor can bypass the sandbox protections to gain remote code execution rights on the host running the sandbox. This vulnerability was patched in the release of version 3.9.11 of vm2. There are no known workarounds.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2022-10-12","github_poc":2,"max_poc_stars":7,"metasploit":0,"nuclei":0,"refs":[{"date":"2022-11-05T13:28:27Z","kind":"github_poc","ref":"https://github.com/prathamhasnotchanged/Exploit-For-CVE-2022-36067","stars":7,"title":"This repo contains payload for the CVE-2022-36067"},{"date":"2022-10-12T13:09:29Z","kind":"github_poc","ref":"https://github.com/0x1nsomnia/CVE-2022-36067-vm2-POC-webapp","stars":2,"title":null}],"tier":"weaponised"},"has_fix":true,"headline":"vm2 vulnerable to Sandbox Escape before v3.9.11","id":"CVE-2022-36067","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2022"},"n_packages":2,"n_references":6,"next":{"headline":"Discourse moderators can edit themes via the API","id":"CVE-2022-36068"},"packages":[{"ecosystem":"npm","fixed":["3.9.11"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-mrgp-mrhc-5jrq"},{"ecosystem":"npm","fixed":["3.9.11"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-mrgp-mrhc-5jrq"}],"prev":{"headline":"Discourse vulnerable to RCE via admins uploading maliciously zipped file","id":"CVE-2022-36066"},"products":["vm2"],"published":"2022-09-06","related":[{"cvss_score":10,"headline":"vm2: Sandbox Escape","id":"CVE-2026-43997","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":10,"headline":"vm2: Sandbox escape","id":"CVE-2026-44005","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":10,"headline":"vm2: Sandbox Escape","id":"CVE-2026-44006","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":10,"headline":"vm2 Sandbox Escape vulnerability","id":"CVE-2023-29017","kev_date_added":null,"published":"2023-04-06"},{"cvss_score":9.9,"headline":"vm2: NodeVM builtin allowlist bypass via `module` builtin's `Module._load` allows sandbox escape","id":"CVE-2026-43999","kev_date_added":null,"published":"2026-05-13"},{"cvss_score":9.8,"headline":"vm2: Snabox breakout via `neutralizeArraySpeciesBatch`","id":"CVE-2026-44008","kev_date_added":null,"published":"2026-05-13"}],"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":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-22","vendors":["patriksimek"]},"summary":"Attackers can bypass sandbox protections in vm2 to execute arbitrary code on the host system.","url":"https://insights.sbomify.com/CVE-2022-36067/"}