{"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-2026-44008 exists.","fix":"Upgrade vm2 to 3.11.2 or later.","what":"CVE-2026-44008 is a critical code injection vulnerability in patriksimek vm2, published on 13 May 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-44008 and fix it if it is affected.\n\nWhat it is: CVE-2026-44008 is a critical code injection vulnerability in patriksimek vm2, published on 13 May 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-44008 exists.\n\nAffected packages and fixed versions:\n- vm2 (npm): affected all versions; fixed in 3.11.2\n- vm2 (npm): affected all versions; fixed in 3.11.2\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-44008/ (Markdown: https://insights.sbomify.com/CVE-2026-44008/index.md)","id":"CVE-2026-44008","markdown":"https://insights.sbomify.com/CVE-2026-44008/index.md","name":"CVE-2026-44008","record":{"aliases":["ECHO-7225-874a-912c","GHSA-9qj6-qjgg-37qq","ROOT-APP-NPM-CVE-2026-44008"],"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 commands on the host system via a prototype getter vulnerability.","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":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-1100","name":"Insufficient Isolation of System-Dependent Functions"},{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.2, the new method neutralizeArraySpeciesBatch works with objects from the other side but can call into this side via getter on the array prototype exposing objects of the wrong side into the sandbox. This can be used to get host objects and get the host Function object. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This vulnerability is fixed in 3.11.2.","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: Snabox breakout via `neutralizeArraySpeciesBatch`","id":"CVE-2026-44008","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"vm2: Sandbox Breakout Through Null Proto Exception","id":"CVE-2026-44009"},"packages":[{"ecosystem":"npm","fixed":["3.11.2"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-9qj6-qjgg-37qq"},{"ecosystem":"npm","fixed":["3.11.2"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-9qj6-qjgg-37qq"}],"prev":{"headline":"vm2: nesting: true bypasses require: false, allowing sandbox escape to arbitrary OS command execution","id":"CVE-2026-44007"},"products":["vm2"],"published":"2026-05-13","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":10,"headline":"vm2 vulnerable to Sandbox Escape before v3.9.11","id":"CVE-2022-36067","kev_date_added":null,"published":"2022-09-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"}],"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)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-07","vendors":["patriksimek"]},"summary":"Attackers can escape the VM2 sandbox to execute arbitrary commands on the host system via a prototype getter vulnerability.","url":"https://insights.sbomify.com/CVE-2026-44008/"}