<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Thu, 08 Oct 2026 15:18:15 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-93605 — vm2 NodeVM before 3.12.1 Remote Code Execution via child_process</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-93605</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; patriksimek vm2&lt;/p&gt;
&lt;p&gt;vm2 NodeVM versions before 3.12.1 contain a sandbox escape vulnerability where the DANGEROUS_BUILTINS denylist omits child_process despite blocking other host-spawning modules. Attackers can require child_process and execute arbitrary commands on the host system when NodeVM is configured with builtin:[&amp;#39;*&amp;#39;] or explicit child_process allowance.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; patriksimek vm2&lt;/p&gt;
&lt;p&gt;vm2 NodeVM versions before 3.12.1 contain a sandbox escape vulnerability where the DANGEROUS_BUILTINS denylist omits child_process despite blocking other host-spawning modules. Attackers can require child_process and execute arbitrary commands on the host system when NodeVM is configured with builtin:[&amp;#39;*&amp;#39;] or explicit child_process allowance.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-93605</guid>
    </item>
    <item>
      <title>GHSA-pq68-rvw4-xp4r — vm2 contains a sandbox escape vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-pq68-rvw4-xp4r</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: vm2&lt;/p&gt;
&lt;p&gt;vm2 NodeVM versions before 3.12.1 contain a sandbox escape vulnerability where the DANGEROUS_BUILTINS denylist omits child_process despite blocking other host-spawning modules. Attackers can require child_process and execute arbitrary commands on the host system when NodeVM is configured with builtin:[&amp;#39;*&amp;#39;] or explicit child_process allowance.&lt;/p&gt;
&lt;p&gt;This fork hardens `NodeVM` with a `DANGEROUS_BUILTINS` denylist that blocks host‑code‑reaching core modules **even when the sandbox requests `builtin:[&amp;#39;*&amp;#39;]` or names them explicitly** — the list contains `module`, `worker_threads`, `cluster`, `vm`, `repl`, `inspector`, `process`, `trace_events`, `wasi`, `diagnostics_channel`, `async_hooks`, `perf_hooks`, `v8`, `os`, `dns`, and `test`. It **omits `child_process`** — the single most direct command‑execution primitive. As a result, a sandbox running under `require:{builtin:[&amp;#39;*&amp;#39;]}` (or the fork&amp;#39;s own documented `[&amp;#39;*&amp;#39;,&amp;#39;-http&amp;#39;,&amp;#39;-net&amp;#39;,…]` subtract pattern) can `require(&amp;#39;child_process&amp;#39;).execSync(...)` and execute arbitrary commands on the host. The omission is internally inconsistent: `cluster` is denied with the explicit rationale &amp;#34;`cluster.fork()` spawns a host child process running attacker‑controlled code,&amp;#34; yet `child_process` — which spawns host processes more directly — is not.&lt;/p&gt;
&lt;p&gt;### Details
`lib/builtin.js`:
- `DANGEROUS_BUILTINS` (lines **83‑179**) — the Set of denied builtins. `child_process` does not appear anywhere in it.
- `isDangerousBuiltin(key)` (lines **185‑195**) — strips `node…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: vm2&lt;/p&gt;
&lt;p&gt;vm2 NodeVM versions before 3.12.1 contain a sandbox escape vulnerability where the DANGEROUS_BUILTINS denylist omits child_process despite blocking other host-spawning modules. Attackers can require child_process and execute arbitrary commands on the host system when NodeVM is configured with builtin:[&amp;#39;*&amp;#39;] or explicit child_process allowance.&lt;/p&gt;
&lt;p&gt;This fork hardens `NodeVM` with a `DANGEROUS_BUILTINS` denylist that blocks host‑code‑reaching core modules **even when the sandbox requests `builtin:[&amp;#39;*&amp;#39;]` or names them explicitly** — the list contains `module`, `worker_threads`, `cluster`, `vm`, `repl`, `inspector`, `process`, `trace_events`, `wasi`, `diagnostics_channel`, `async_hooks`, `perf_hooks`, `v8`, `os`, `dns`, and `test`. It **omits `child_process`** — the single most direct command‑execution primitive. As a result, a sandbox running under `require:{builtin:[&amp;#39;*&amp;#39;]}` (or the fork&amp;#39;s own documented `[&amp;#39;*&amp;#39;,&amp;#39;-http&amp;#39;,&amp;#39;-net&amp;#39;,…]` subtract pattern) can `require(&amp;#39;child_process&amp;#39;).execSync(...)` and execute arbitrary commands on the host. The omission is internally inconsistent: `cluster` is denied with the explicit rationale &amp;#34;`cluster.fork()` spawns a host child process running attacker‑controlled code,&amp;#34; yet `child_process` — which spawns host processes more directly — is not.&lt;/p&gt;
&lt;p&gt;### Details
`lib/builtin.js`:
- `DANGEROUS_BUILTINS` (lines **83‑179**) — the Set of denied builtins. `child_process` does not appear anywhere in it.
- `isDangerousBuiltin(key)` (lines **185‑195**) — strips `node…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-pq68-rvw4-xp4r</guid>
    </item>
  </channel>
</rss>
