CVE-2026-26833: thumbler · Code Injection
Affects thumblerSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 2.3% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
npmthumblerpkg:npm/thumblerOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official fix is available, avoid using vulnerable versions of thumbler or restrict access to the affected functionality to trusted users only. Do not rely on generic mitigations as the vulnerability stems from unsafe command construction in the code.
Description
thumbler versions through 1.1.2 contain a critical OS command injection vulnerability in the thumbnail() function. This occurs because user-supplied input in the input, output, time, or size parameters is directly concatenated into a shell command executed via child_process.exec() without proper sanitization or escaping. The vulnerability has a CVSS score of 9.8, indicating critical severity with high impact on confidentiality, integrity, and availability. No patch or official remediation information is currently provided.