https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 18:51:20 +0000 https://db.gcve.eu/vuln/cve-2026-92958 <p><strong>Affected:</strong> patriksimek vm2</p> <p>vm2 through 3.11.6 contains a builtin-module denylist bypass in NodeVM. When the embedder uses the builtin wildcard together with negative entries (e.g. require: { builtin: [&#39;*&#39;, &#39;-fs&#39;, &#39;-child_process&#39;] }), negative entries are matched by exact module name in lib/builtin.js, so -fs removes only the builtin named fs and does not remove builtin subpaths such as fs/promises. Sandboxed code can therefore call require(&#39;fs/promises&#39;) or require(&#39;node:fs/promises&#39;) and reach the promise-based filesystem API despite fs being denied; node: prefix handling is likewise inconsistent (a -node:fs/promises entry does not block require(&#39;fs/promises&#39;)). Host file creation and writing were confirmed via fsp.writeFile(), and other fs/promises operations (cp, mkdir, rename, rm, rmdir, truncate, read operations, etc.) are also reachable. This issue is fixed in vm2 3.11.7.</p> <p><strong>Affected:</strong> patriksimek vm2</p> <p>vm2 through 3.11.6 contains a builtin-module denylist bypass in NodeVM. When the embedder uses the builtin wildcard together with negative entries (e.g. require: { builtin: [&#39;*&#39;, &#39;-fs&#39;, &#39;-child_process&#39;] }), negative entries are matched by exact module name in lib/builtin.js, so -fs removes only the builtin named fs and does not remove builtin subpaths such as fs/promises. Sandboxed code can therefore call require(&#39;fs/promises&#39;) or require(&#39;node:fs/promises&#39;) and reach the promise-based filesystem API despite fs being denied; node: prefix handling is likewise inconsistent (a -node:fs/promises entry does not block require(&#39;fs/promises&#39;)). Host file creation and writing were confirmed via fsp.writeFile(), and other fs/promises operations (cp, mkdir, rename, rm, rmdir, truncate, read operations, etc.) are also reachable. This issue is fixed in vm2 3.11.7.</p> https://db.gcve.eu/vuln/cve-2026-92958