Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.8amended

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

CVE-2025-63705GHSA-8jh2-3mw6-6pfm

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm node-ts-ocr

    Affected
    >= 1.0.15, <= 1.0.15
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.8 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2025-63705: 1.19% estimated exploitation activity in the next 30 days; percentile 67.86 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-8jh2-3mw6-6pfm

  2. Revision 1 · created ·

    Published from osv record GHSA-8jh2-3mw6-6pfm

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-63705

Advisory: node-ts-ocr is vulnerable to OS Command Injection via the invokeImageOcr function in src/index.js
IDs: CVE-2025-63705, GHSA-8jh2-3mw6-6pfm
Record: https://patchnext.com/advisories/cve-2025-63705 (revision 2, source checked 26 Oct 2026, 12:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm node-ts-ocr: affected >= 1.0.15, <= 1.0.15

## Suggested inspection (read-only)
- `npm ls node-ts-ocr --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on node-ts-ocr.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8jh2-3mw6-6pfm (OSV record GHSA-8jh2-3mw6-6pfm lists affected ranges: npm node-ts-ocr >=1.0.15 <=1.0.15)
- Verified: https://github.com/advisories/GHSA-8jh2-3mw6-6pfm (GitHub-reviewed advisory GHSA-8jh2-3mw6-6pfm lists affected ranges: npm node-ts-ocr >=1.0.15 <=1.0.15)

Commands are suggestions: review each one before running it.

Loading voting…