{"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-44001 exists.","fix":"Upgrade vm2 to 3.11.0 or later.","what":"CVE-2026-44001 is a high-severity vulnerability in patriksimek vm2, published on 13 May 2026."},"fix_prompt":"Check this codebase for CVE-2026-44001 and fix it if it is affected.\n\nWhat it is: CVE-2026-44001 is a high-severity vulnerability in patriksimek vm2, published on 13 May 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44001 exists.\n\nAffected packages and fixed versions:\n- vm2 (npm): affected all versions; fixed in 3.11.0\n- vm2 (npm): affected all versions; fixed in 3.11.0\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-44001/ (Markdown: https://insights.sbomify.com/CVE-2026-44001/index.md)","id":"CVE-2026-44001","markdown":"https://insights.sbomify.com/CVE-2026-44001/index.md","name":"CVE-2026-44001","record":{"aliases":["GHSA-hw58-p9xv-2mjh","ROOT-APP-NPM-CVE-2026-44001"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[{"product":"vm2","vendor":"vm2_project"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-248","name":"Uncaught Exception"}],"description":"vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.0, a sandbox escape vulnerability in vm2 v3.10.5 allows any sandboxed code to crash the host Node.js process via a single Promise constructor that triggers an unhandled rejection propagating to the host. The fix for CVE-2026-22709 (v3.10.2) only sanitized the onRejected callback in .then() and .catch() overrides and did not address the executor-to-unhandledRejection path. This vulnerability is fixed in 3.11.0.","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 Promise Constructor Unhandled Rejection (Process Crash DoS)","id":"CVE-2026-44001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"vm2: Host File Path Disclosure via Stack Trace Information Leak","id":"CVE-2026-44002"},"packages":[{"ecosystem":"npm","fixed":["3.11.0"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-hw58-p9xv-2mjh"},{"ecosystem":"npm","fixed":["3.11.0"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-hw58-p9xv-2mjh"}],"prev":{"headline":"vm2: sandbox boundary bypass via host Promise resolution preserving host object identity","id":"CVE-2026-44000"},"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"},{"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)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-07","vendors":["patriksimek"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-44001/"}