https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 08 Oct 2026 22:34:30 +0000 https://vulnerability.circl.lu/vuln/cve-2026-92946 <p><strong>Affected:</strong> patriksimek vm2</p> <p>vm2 before 3.11.7 contains a remote code execution vulnerability when require.external is enabled without an explicit require.root that excludes node_modules. Sandboxed code can require vm2&#39;s own package, instantiate an unrestricted NodeVM instance, and execute arbitrary host OS commands via child_process.</p> <p><strong>Affected:</strong> patriksimek vm2</p> <p>vm2 before 3.11.7 contains a remote code execution vulnerability when require.external is enabled without an explicit require.root that excludes node_modules. Sandboxed code can require vm2&#39;s own package, instantiate an unrestricted NodeVM instance, and execute arbitrary host OS commands via child_process.</p> https://vulnerability.circl.lu/vuln/cve-2026-92946 https://vulnerability.circl.lu/vuln/ghsa-j3hm-6rg5-mchv <p><strong>Affected:</strong> npm: vm2</p> <p>## Summary</p> <p>`NodeVM`&#39;s `require.external` option lets sandboxed code `require()` local files and npm packages. When `require.external` is enabled and `require.root` is **not explicitly set to a path that excludes `node_modules`**, two defaults combine to fully defeat the sandbox:</p> <p>- `require.root` defaults to **unrestricted** — &#34;if omitted every path is allowed.&#34; - `require.context` defaults to **`&#34;host&#34;`** — files loaded this way run through the **real Node.js `require()`**, not inside any vm2 sandbox.</p> <p>Sandboxed code can therefore `require()` a relative or absolute path to vm2&#39;s own installed package (`node_modules/vm2`), obtain the real, unwrapped `NodeVM`/`VM` classes, construct a brand-new **unrestricted** nested `NodeVM` instance, and execute arbitrary host OS commands via `child_process`.</p> <p>This is exploitable using **vm2&#39;s own documented &#34;Quick Examples&#34; configuration** in `README.md`:</p> <p>```js const vm = new NodeVM({ require: { external: true, root: &#39;./&#39;, }, }); ```</p> <p>`root: &#39;./&#39;` reads as a safety restriction but, in any ordinary npm project layout, `./node_modules/vm2` sits inside that same directory tree — so the restriction does not exclude vm2 itself. An application built by following the README&#39;s quick-start guide is affected by default.</p> <p>## Affected Versions</p> <p>All vm2 versions where `lib/resolver-compat.js`&#39;s `makeResolverFromLegacyOptions` predates this report — confirmed present as of the current `main` (post-3.11.5, including all fixes through GHSA…</p> <p><strong>Affected:</strong> npm: vm2</p> <p>## Summary</p> <p>`NodeVM`&#39;s `require.external` option lets sandboxed code `require()` local files and npm packages. When `require.external` is enabled and `require.root` is **not explicitly set to a path that excludes `node_modules`**, two defaults combine to fully defeat the sandbox:</p> <p>- `require.root` defaults to **unrestricted** — &#34;if omitted every path is allowed.&#34; - `require.context` defaults to **`&#34;host&#34;`** — files loaded this way run through the **real Node.js `require()`**, not inside any vm2 sandbox.</p> <p>Sandboxed code can therefore `require()` a relative or absolute path to vm2&#39;s own installed package (`node_modules/vm2`), obtain the real, unwrapped `NodeVM`/`VM` classes, construct a brand-new **unrestricted** nested `NodeVM` instance, and execute arbitrary host OS commands via `child_process`.</p> <p>This is exploitable using **vm2&#39;s own documented &#34;Quick Examples&#34; configuration** in `README.md`:</p> <p>```js const vm = new NodeVM({ require: { external: true, root: &#39;./&#39;, }, }); ```</p> <p>`root: &#39;./&#39;` reads as a safety restriction but, in any ordinary npm project layout, `./node_modules/vm2` sits inside that same directory tree — so the restriction does not exclude vm2 itself. An application built by following the README&#39;s quick-start guide is affected by default.</p> <p>## Affected Versions</p> <p>All vm2 versions where `lib/resolver-compat.js`&#39;s `makeResolverFromLegacyOptions` predates this report — confirmed present as of the current `main` (post-3.11.5, including all fixes through GHSA…</p> https://vulnerability.circl.lu/vuln/ghsa-j3hm-6rg5-mchv