{"answers":{"affected":"2 open source packages ship an affected version, including vm2.","exploited":"There is no known exploitation of CVE-2026-47135 in the wild and no public exploit code.","fix":"Upgrade vm2 to 3.11.4 or later.","what":"CVE-2026-47135 is a high-severity code injection vulnerability in patriksimek vm2, published on 12 Jun 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-47135 and fix it if it is affected.\n\nWhat it is: CVE-2026-47135 is a high-severity code injection vulnerability in patriksimek vm2, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-47135 in the wild and no public exploit code.\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-47135/ (Markdown: https://insights.sbomify.com/CVE-2026-47135/index.md)","id":"CVE-2026-47135","markdown":"https://insights.sbomify.com/CVE-2026-47135/index.md","name":"CVE-2026-47135","record":{"aliases":["ECHO-3377-7de8-77cf","GHSA-m5q2-4fm3-vfqp","MINI-9q29-2736-7qp5","ROOT-APP-NPM-CVE-2026-47135"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"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 code on the host by exploiting unblocked cross-realm symbols.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"description":"vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, Symbol.for override in setup-sandbox.js only intercepts 2 of 9 dangerous Node.js cross-realm symbols. Combined with the bridge's set/defineProperty/deleteProperty traps having no isDangerousCrossRealmSymbol key check, sandbox code can obtain real cross-realm symbols, write them to host objects, and control host-side behavior — verified with a full util.promisify hijack chain. This issue has been patched in version 3.11.4.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"vm2: Sandbox escape via unblocked cross-realm Symbol.for keys + missing bridge write-trap symbol checks","id":"CVE-2026-47135","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"RustFS: Unauthenticated RustFS console license endpoint exposes license metadata","id":"CVE-2026-47136"},"packages":[{"ecosystem":"npm","fixed":["3.11.4"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-m5q2-4fm3-vfqp"},{"ecosystem":"npm","fixed":["3.11.4"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-m5q2-4fm3-vfqp"}],"prev":{"headline":"Security feature bypass in clearancekit","id":"CVE-2026-47134"},"products":["vm2"],"published":"2026-06-12","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-13","vendors":["patriksimek"]},"summary":"Attackers can escape the vm2 sandbox to execute arbitrary code on the host by exploiting unblocked cross-realm symbols.","url":"https://insights.sbomify.com/CVE-2026-47135/"}