{"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-92953 exists.","fix":"Upgrade vm2 to 3.11.8 or later.","what":"CVE-2026-92953 is a critical code injection vulnerability in patriksimek vm2, published on 17 Sep 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-92953 and fix it if it is affected.\n\nWhat it is: CVE-2026-92953 is a critical code injection vulnerability in patriksimek vm2, published on 17 Sep 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-92953 exists.\n\nAffected packages and fixed versions:\n- vm2 (npm): affected from 3.11.0; fixed in 3.11.8\n- vm2 (npm): affected from 3.11.0; fixed in 3.11.8\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-92953/ (Markdown: https://insights.sbomify.com/CVE-2026-92953/index.md)","id":"CVE-2026-92953","markdown":"https://insights.sbomify.com/CVE-2026-92953/index.md","name":"CVE-2026-92953","record":{"aliases":["CLEANSTART-2026-NR22907","ECHO-68ba-f48a-b95f","GHSA-3vgf-8m4q-q4qr","MINI-4v84-226r-5288","ROOT-APP-NPM-CVE-2026-92953"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript sandbox library","requires_auth":"none","summary":"Attackers can escape the vm2 sandbox via prototype pollution to execute arbitrary code on the host system.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-913","name":"Improper Control of Dynamically-Managed Code Resources"}],"description":"vm2 versions from 3.11.0 before 3.11.8 fail to protect host TypedArray and ArrayBuffer prototypes from sandbox mutation. Attackers can use prototype-walking primitives to reach and modify host Uint8Array.prototype, %TypedArray%.prototype, and ArrayBuffer.prototype, causing host-created typed arrays to observe attacker-controlled properties after VM.run() returns.","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 3.11.0 through 3.11.7 Prototype Pollution via TypedArray","id":"CVE-2026-92953","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"vm2 3.10.0 through 3.11.7 Denial of Service via Host Promise","id":"CVE-2026-92954"},"packages":[{"ecosystem":"npm","fixed":["3.11.8"],"introduced":["3.11.0"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-3vgf-8m4q-q4qr"},{"ecosystem":"npm","fixed":["3.11.8"],"introduced":["3.11.0"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-3vgf-8m4q-q4qr"}],"prev":{"headline":"vm2 3.11.4 through 3.11.6 Sandbox Symbol Filtering Bypass","id":"CVE-2026-92952"},"products":["vm2"],"published":"2026-09-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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-18","vendors":["patriksimek"]},"summary":"Attackers can escape the vm2 sandbox via prototype pollution to execute arbitrary code on the host system.","url":"https://insights.sbomify.com/CVE-2026-92953/"}