{"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-47141 exists.","fix":"Upgrade vm2 to 3.11.4 or later.","what":"CVE-2026-47141 is a medium-severity 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-47141 and fix it if it is affected.\n\nWhat it is: CVE-2026-47141 is a medium-severity 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-47141 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-47141/ (Markdown: https://insights.sbomify.com/CVE-2026-47141/index.md)","id":"CVE-2026-47141","markdown":"https://insights.sbomify.com/CVE-2026-47141/index.md","name":"CVE-2026-47141","record":{"aliases":["ECHO-4102-701c-2063","GHSA-9g8x-92q2-p28f","MINI-6qmh-9p38-8276","ROOT-APP-NPM-CVE-2026-47141"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Node.js sandbox library","requires_auth":"none","summary":"Sandboxed code can leak host process and HTTP data via observability builtins if require.builtin is configured to allow them.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","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:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.4, NodeVM exposes some process-wide observability builtins when they are allowed through require.builtin. The diagnostics_channel, async_hooks, and perf_hooks builtins are not blocked by the dangerous builtin denylist. These modules are process-wide, not sandbox-local. Sandboxed code can use them to observe host application data across the vm2 boundary. 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":"weaponised"},"has_fix":true,"headline":"vm2: NodeVM observability builtins leak host process and HTTP request data","id":"CVE-2026-47141","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Capstone has a NULL Pointer Dereference with 3DNow! opcodes","id":"CVE-2026-47143"},"packages":[{"ecosystem":"npm","fixed":["3.11.4"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":null,"source":"GHSA-9g8x-92q2-p28f"},{"ecosystem":"npm","fixed":["3.11.4"],"introduced":["0"],"last_affected":[],"package":"vm2","purl":"pkg:npm/vm2","source":"GHSA-9g8x-92q2-p28f"}],"prev":{"headline":"vm2: NodeVM builtin denylist bypass via process and inspector/promises allows host code execution","id":"CVE-2026-47140"},"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-13","vendors":["patriksimek"]},"summary":"Sandboxed code can leak host process and HTTP data via observability builtins if require.builtin is configured to allow them.","url":"https://insights.sbomify.com/CVE-2026-47141/"}