# CVE-2025-63705: node-ts-ocr is vulnerable to OS Command Injection via the invokeImageOcr function in src/index.js

> Attackers can execute arbitrary OS commands via the invokeImageOcr function in the node-ts-ocr npm package.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 May 2026
- **Updated:** 8 May 2026
- **Also known as:** GHSA-8jh2-3mw6-6pfm

## What is CVE-2025-63705?

CVE-2025-63705 is a high-severity command injection vulnerability in n/a, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

NPM package node-ts-ocr 1.0.15 is vulnerable to OS Command Injection via the invokeImageOcr function in src/index.js.

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

## Which versions are affected by CVE-2025-63705?

2 open source packages ship an affected version, including node-ts-ocr.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `node-ts-ocr` | npm | All versions | None |
| `node-ts-ocr` | npm | All versions | None |

## How do I fix CVE-2025-63705?

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

## Is CVE-2025-63705 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63705 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63705 and fix it if it is affected.

What it is: CVE-2025-63705 is a high-severity command injection vulnerability in n/a, published on 7 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63705 exists.

Affected packages and fixed versions:
- node-ts-ocr (npm): affected all versions; no fix listed
- node-ts-ocr (npm): affected all versions; no fix listed

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-2025-63705/ (Markdown: https://insights.sbomify.com/CVE-2025-63705/index.md)
```

## Sources

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

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