Skip to main content
VulnerabilityPublished

CVE-2026-26832: node-tesseract-ocr · OS Command Injection

Affects node-tesseract-ocrSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.7% chance of exploitation in 30 days – higher than 77% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AC:L/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
npmnode-tesseract-ocrpkg:npm/node-tesseract-ocrOther threatsAffected
  • <=2.2.1
Fixed in–

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

AI-suggested

To mitigate this vulnerability, organizations should immediately audit their use of node-tesseract-ocr and avoid passing unsanitized user input to the recognize() function. Implement strict input validation and sanitization to ensure file path parameters do not contain shell metacharacters or unexpected commands. Where possible, replace child_process.exec() with safer alternatives such as child_process.execFile() or spawn(), which do not invoke a shell and reduce injection risk. Monitor for updates or patches from the package maintainers and apply them promptly once available. As a temporary measure, consider sandboxing the Node.js process or running it with minimal privileges to limit potential damage. Additionally, implement network-level protections such as web application firewalls (WAFs) to detect and block suspicious command injection attempts targeting OCR-related endpoints.

Description

node-tesseract-ocr is an npm package that provides a Node.js wrapper for Tesseract OCR. In all versions through 2.2.1, the recognize() function in src/index.js is vulnerable to OS Command Injection. The file path parameter is concatenated into a shell command string and passed to child_process.exec() without proper sanitization

References

Community reviews

Loading reviews…