Skip to main content
VulnerabilityPublished Updated

CVE-2026-104849: tinylibs tinypool · Code Injection

Affects tinylibs tinypoolSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.5 Critical : upgrade to 2.1.2 as a priority.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
9.5Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.1.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade tinylibs tinypool to 2.1.2.

Affected software

ProductAffectedFixed in
tinylibstinypoolAffected
  • <2.1.2
Fixed in
  • 2.1.2
npmtinypoolpkg:npm/tinypoolOther threatsAffected
  • <2.1.2
Fixed in
  • 2.1.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade tinypool to version 2.1.2 or later, where this vulnerability is fixed. Applications that do not pass a custom options object to pool.run() are not affected. There is no indication of alternative mitigations or temporary fixes; applying the official update is the recommended remediation.

Description

Tinypool versions prior to 2.1.2 contain a code injection vulnerability due to improper handling of the filename property in the options object passed to pool.run(). An attacker who can pollute Object.prototype.filename can cause the worker pool to load malicious JavaScript code, potentially leading to arbitrary code execution with the host process's privileges. This vulnerability is fixed in version 2.1.2.

References

Community reviews

Loading reviews…