<?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>Wed, 07 Oct 2026 04:01:42 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-382421</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-382421</link>
      <description>EUVD-2026-382421</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-382421</guid>
    </item>
    <item>
      <title>fkie_cve-2026-104848</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-104848</link>
      <description>&lt;p&gt;Tinypool is a minimal Node.js worker thread pool implementation. Prior to 2.1.1, Tinypool constructs ThreadPool.options from a normal options object and reads the execArgv and env worker options in dist/index.js, allowing values inherited from a polluted Object.prototype to be copied into own properties and passed to worker_threads.Worker. An attacker who can first pollute either property can cause each newly spawned worker to load attacker-selected JavaScript through command-line preload arguments or NODE_OPTIONS, resulting in code execution with the host process&amp;#39;s privileges and possible access to CI secrets, signing material, or build artifacts. This issue is fixed in version 2.1.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Tinypool is a minimal Node.js worker thread pool implementation. Prior to 2.1.1, Tinypool constructs ThreadPool.options from a normal options object and reads the execArgv and env worker options in dist/index.js, allowing values inherited from a polluted Object.prototype to be copied into own properties and passed to worker_threads.Worker. An attacker who can first pollute either property can cause each newly spawned worker to load attacker-selected JavaScript through command-line preload arguments or NODE_OPTIONS, resulting in code execution with the host process&amp;#39;s privileges and possible access to CI secrets, signing material, or build artifacts. This issue is fixed in version 2.1.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-104848</guid>
    </item>
    <item>
      <title>GHSA-5gmw-xhrv-c9v3 — Tinypool: Prototype Pollution gadget in worker options leads to Remote Code Execution</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5gmw-xhrv-c9v3</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: tinypool&lt;/p&gt;
&lt;p&gt;`tinypool` passes worker options to `new Worker()` by reading them off a plain object whose prototype is `Object.prototype`. Options the application did not set are resolved through the prototype chain and then passed explicitly to `worker_threads.Worker`.&lt;/p&gt;
&lt;p&gt;Node core ignores `Worker` options inherited from `Object.prototype`. By reading them and passing them explicitly, tinypool re-materialises them as own properties and defeats that protection.&lt;/p&gt;
&lt;p&gt;Two keys reach code execution:&lt;/p&gt;
&lt;p&gt;1. **`execArgv`** — polluting `Object.prototype.execArgv = [&amp;#39;--require&amp;#39;, &amp;#39;/path/to/attacker.js&amp;#39;]` causes every pool worker to load the attacker&amp;#39;s script.
2. **`env`** — polluting `Object.prototype.env = { NODE_OPTIONS: &amp;#39;--require /path/to/attacker.js&amp;#39; }` achieves the same via environment injection.&lt;/p&gt;
&lt;p&gt;## Root cause&lt;/p&gt;
&lt;p&gt;`dist/index.js` lines 508-511:&lt;/p&gt;
&lt;p&gt;```js
env:            this.options.env,
argv:           this.options.argv,
execArgv:       this.options.execArgv,
resourceLimits: this.options.resourceLimits,
```&lt;/p&gt;
&lt;p&gt;`this.options` is built at line 470 via object spread:&lt;/p&gt;
&lt;p&gt;```js
this.options = { ...kDefaultOptions, ...options, filename, maxQueue: 0 };
```&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Arbitrary code execution inside every worker the pool spawns, with the privileges of the host process. Because tinypool is the worker pool behind Vitest (~42M downloads/week), the natural blast radius is developer machines and CI runners — an attacker who lands a prototype-pollution primitive anywhere in the dependency tree gets code execution in th…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: tinypool&lt;/p&gt;
&lt;p&gt;`tinypool` passes worker options to `new Worker()` by reading them off a plain object whose prototype is `Object.prototype`. Options the application did not set are resolved through the prototype chain and then passed explicitly to `worker_threads.Worker`.&lt;/p&gt;
&lt;p&gt;Node core ignores `Worker` options inherited from `Object.prototype`. By reading them and passing them explicitly, tinypool re-materialises them as own properties and defeats that protection.&lt;/p&gt;
&lt;p&gt;Two keys reach code execution:&lt;/p&gt;
&lt;p&gt;1. **`execArgv`** — polluting `Object.prototype.execArgv = [&amp;#39;--require&amp;#39;, &amp;#39;/path/to/attacker.js&amp;#39;]` causes every pool worker to load the attacker&amp;#39;s script.
2. **`env`** — polluting `Object.prototype.env = { NODE_OPTIONS: &amp;#39;--require /path/to/attacker.js&amp;#39; }` achieves the same via environment injection.&lt;/p&gt;
&lt;p&gt;## Root cause&lt;/p&gt;
&lt;p&gt;`dist/index.js` lines 508-511:&lt;/p&gt;
&lt;p&gt;```js
env:            this.options.env,
argv:           this.options.argv,
execArgv:       this.options.execArgv,
resourceLimits: this.options.resourceLimits,
```&lt;/p&gt;
&lt;p&gt;`this.options` is built at line 470 via object spread:&lt;/p&gt;
&lt;p&gt;```js
this.options = { ...kDefaultOptions, ...options, filename, maxQueue: 0 };
```&lt;/p&gt;
&lt;p&gt;## Impact&lt;/p&gt;
&lt;p&gt;Arbitrary code execution inside every worker the pool spawns, with the privileges of the host process. Because tinypool is the worker pool behind Vitest (~42M downloads/week), the natural blast radius is developer machines and CI runners — an attacker who lands a prototype-pollution primitive anywhere in the dependency tree gets code execution in th…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5gmw-xhrv-c9v3</guid>
    </item>
  </channel>
</rss>
