Vulnerability in tinypool (CVE-2026-104848)
Summary
Vulnerability in tinypool (CVE-2026-104848). Risk of unauthorized operations or information disclosure. Exploitable via tinypool. Mitigation: upgrade to 2.1.1 or later.
Original description
The description as published by the source.
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.
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.
Two keys reach code execution:
execArgv— pollutingObject.prototype.execArgv = ['--require', '/path/to/attacker.js']causes every pool worker to load the attacker's script.env— pollutingObject.prototype.env = { NODE_OPTIONS: '--require /path/to/attacker.js' }achieves the same via environment injection.
Root cause
dist/index.js lines 508-511:
env: this.options.env,
argv: this.options.argv,
execArgv: this.options.execArgv,
resourceLimits: this.options.resourceLimits,
this.options is built at line 470 via object spread:
this.options = { ...kDefaultOptions, ...options, filename, maxQueue: 0 };
Impact
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 the…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-104848 has been found in tinypool.
Attackers can target a specific entry point like tinypool over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade tinypool to 2.1.1 or later.
If unsure, ask your IT team or search "tinypool CVE-2026-104848" on the vendor's site.
CVE-2026-104848 (tinypool) — CWE-1321
Attack surface: tinypool / Object.prototype / worker_threads.Worker / Worker
Patched: 2.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-1321) exists in tinypool. Attackers reach the vulnerable code path via tinypool.
Check the vendor advisory for the affected versions of tinypool. Attack surface: tinypool / Object.prototype / worker_threads.Worker / Worker.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.1.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'tinypool' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'tinypool' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
tinypoolを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade tinypool to 2.1.1ステージング環境で 2.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com
- web github.com