# CVE-2026-117511: desmondmorris node-tesseract Command Builder tesseract.js process os command injection


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-7xrv-c458-6gmj

## What is CVE-2026-117511?

CVE-2026-117511 is a medium-severity vulnerability in desmondmorris node-tesseract, published on 27 Oct 2026. 

### Official description

A vulnerability has been found in desmondmorris node-tesseract up to 0.2.7. Affected by this issue is the function process of the file lib/tesseract.js of the component Command Builder. Such manipulation of the argument image leads to os command injection. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-117511?


## How do I fix CVE-2026-117511?

No fix has been published for CVE-2026-117511 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-117511 being exploited?

There is no known exploitation of CVE-2026-117511 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-117511 and fix it if it is affected.

What it is: CVE-2026-117511 is a medium-severity vulnerability in desmondmorris node-tesseract, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-117511 in the wild and no public exploit code.

Affected product: desmondmorris node-tesseract. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-117511/ (Markdown: https://insights.sbomify.com/CVE-2026-117511/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-117511
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-117511
- OSV: https://osv.dev/vulnerability/CVE-2026-117511

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-117511/
Summaries are generated and may contain mistakes; the official description above is the record.