{"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-92962 exists.","fix":"Upgrade vm2 to 3.11.4 or later.","what":"CVE-2026-92962 is a low-severity vulnerability in patriksimek vm2, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-92962 and fix it if it is affected.\n\nWhat it is: CVE-2026-92962 is a low-severity vulnerability in patriksimek vm2, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92962 exists.\n\nAffected packages and fixed versions:\n- vm2 (npm): affected all versions; fixed in 3.11.4\n- vm2 (npm): affected all versions; fixed in 3.11.4\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-92962/ (Markdown: https://insights.sbomify.com/CVE-2026-92962/index.md)","id":"CVE-2026-92962","markdown":"https://insights.sbomify.com/CVE-2026-92962/index.md","name":"CVE-2026-92962","record":{"aliases":["ECHO-b5b8-7f40-339a","GHSA-2c9f-f88g-g76p","GHSA-q3fm-4wcw-g57x","MINI-m82w-4qp7-ch75"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"JavaScript sandbox library","requires_auth":"none","summary":"Sandboxed code can intercept stack trace lines via prototype pollution, causing an information side channel in the vm2 JavaScript sandbox library.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":2.1,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:N/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"vm2 is a sandbox for running untrusted JavaScript. In vm2 versions up to and including 3.11.3, the defaultSandboxPrepareStackTrace function in lib/setup-sandbox.js builds its output array using prototype-walking index assignment (lines[lines.length] = value) rather than a prototype-bypassing define-property primitive. Because this bridge-internal array is allocated in the sandbox realm, code inside the sandbox can install an accessor on Array.prototype for the relevant index; the accessor is then invoked whenever the sandbox reads error.stack (or otherwise triggers Error.prepareStackTrace), allowing sandbox code to observe and intercept each stack-trace line written by the bridge. The same pattern is used in the error-handling (catch) branch. The values written are formatted strings only, so the practical impact is limited to an information side channel and a violation of vm2's bridge-container defense invariant rather than a sandbox escape; the vendor rates the issue Low. The issue is fixed in vm2 3.11.4, which installs each entry as an own data property via Reflect.defineProperty.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"vm2 before 3.11.4 Defense Invariant Violation via setup-sandbox.js","id":"CVE-2026-92962","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"vm2 before 3.11.2 Information Disclosure via Internal State","id":"CVE-2026-92963"},"packages":[{"ecosystem":"npm","fixed":["3.11.4"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-q3fm-4wcw-g57x"},{"ecosystem":"npm","fixed":["3.11.4"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-q3fm-4wcw-g57x"}],"prev":{"headline":"vm2 before 3.11.6 Memory Exhaustion DoS via bufferAllocLimit Bypass","id":"CVE-2026-92961"},"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-17","vendors":["patriksimek"]},"summary":"Sandboxed code can intercept stack trace lines via prototype pollution, causing an information side channel in the vm2 JavaScript sandbox library.","url":"https://insights.sbomify.com/CVE-2026-92962/"}