{"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-92936 exists.","fix":"Upgrade vm2 to 3.11.7 or later.","what":"CVE-2026-92936 is a medium-severity 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-92936 and fix it if it is affected.\n\nWhat it is: CVE-2026-92936 is a medium-severity 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-92936 exists.\n\nAffected packages and fixed versions:\n- vm2 (npm): affected from 3.11.0; fixed in 3.11.7\n- vm2 (npm): affected from 3.11.0; fixed in 3.11.7\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-92936/ (Markdown: https://insights.sbomify.com/CVE-2026-92936/index.md)","id":"CVE-2026-92936","markdown":"https://insights.sbomify.com/CVE-2026-92936/index.md","name":"CVE-2026-92936","record":{"aliases":["ECHO-b9fc-a52a-f0b3","GHSA-x6m4-chr9-cg97","MINI-4r2m-h48r-wxx7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js sandbox library","requires_auth":"none","summary":"Sandboxed code can leak absolute host filesystem paths and internal function names via error stack traces, exposing sensitive system information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"vm2 versions 3.11.0 through 3.11.6 leak absolute host filesystem paths to sandboxed code through error stack formatting. Attacker-supplied code can force the host-realm source transformer to throw a SyntaxError (for example by calling eval with malformed source) and then read the error's .stack property; the bridge forwards the .stack read to the host-realm formatter, bypassing the sandbox-side host-path redaction introduced for GHSA-v27g-jcqj-v8rw. The returned stack string discloses absolute paths from vm2, Node.js internals, and the embedding application's own source tree, along with host function names. Default new VM() and new NodeVM() configurations are affected without any special options, and the issue persists when string eval is disabled because the host-side transformer throws before eval is handled. The impact is information disclosure only; no code execution results. Fixed in vm2 3.11.7.","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 before 3.11.7 Information Disclosure via Error Stack","id":"CVE-2026-92936","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 3.11.6 Remote Code Execution via Promise call/apply","id":"CVE-2026-92937"},"packages":[{"ecosystem":"npm","fixed":["3.11.7"],"introduced":["3.11.0"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-x6m4-chr9-cg97"},{"ecosystem":"npm","fixed":["3.11.7"],"introduced":["3.11.0"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-x6m4-chr9-cg97"}],"prev":{"headline":"vm2 NodeVM Remote Code Execution via Array-Shaped Require","id":"CVE-2026-92935"},"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-17","vendors":["patriksimek"]},"summary":"Sandboxed code can leak absolute host filesystem paths and internal function names via error stack traces, exposing sensitive system information.","url":"https://insights.sbomify.com/CVE-2026-92936/"}