CVE-2025-63705

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-07. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
56(Track*)
EG Risk 56/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
1%
EPSS %ILE
66%
KEV
Not listed

Published

May 7, 2026

Last Modified

May 8, 2026

Advisory Details (1)

Auto-updated May 8, 2026
No patch confirmed yet.
generic

Public disclosure of security issue in NPM package node-ts-ocr through version 1.0.15 · GitHub

https://gist.github.com/6en6ar/a2ac44da0f4e580190be3e66cfbb9a4a

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
npmnode-ts-ocr—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
node-ts-ocr1.0.15——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 231 total refreshes for this CVE.

  1. 2026-09-15 03:10 UTCEPSS rescore
  2. 2026-09-13 16:46 UTCEPSS rescore
  3. 2026-09-12 15:00 UTCEPSS rescore
  4. 2026-09-11 14:52 UTCEPSS rescore
  5. 2026-09-11 09:36 UTCEPSS rescore
  6. 2026-09-10 09:34 UTCEPSS rescore
  7. 2026-09-08 22:00 UTCEPSS rescore
  8. 2026-09-07 16:00 UTCEPSS rescore
  9. 2026-09-06 13:47 UTCEPSS rescore
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:11 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-08-30 19:16 UTCEPSS rescore
  14. 2026-08-30 01:21 UTCEPSS rescore
  15. 2026-08-28 21:40 UTCEPSS rescore
  16. 2026-08-27 14:24 UTCEPSS rescore
  17. 2026-08-26 14:45 UTCEPSS rescore
  18. 2026-08-25 13:48 UTCEPSS rescore
  19. 2026-08-24 14:16 UTCEPSS rescore
  20. 2026-08-23 19:36 UTCEG score recompute
  21. 2026-08-23 19:36 UTCGHSA enrichment
  22. 2026-08-23 00:18 UTCEPSS rescore
  23. 2026-08-21 23:48 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:47 UTCEPSS rescore
  2. 2026-08-17 13:46 UTCEPSS rescore
  3. 2026-08-17 12:44 UTCEG score recompute
  4. 2026-08-17 12:44 UTCGHSA enrichment
  5. 2026-08-16 14:55 UTCEPSS rescore
  6. 2026-08-16 04:44 UTCEG score recompute
  7. 2026-08-16 04:44 UTCGHSA enrichment
  8. 2026-08-16 02:13 UTCEPSS rescore
  9. 2026-08-15 01:30 UTCEPSS rescore
  10. 2026-08-15 01:29 UTCEPSS rescore
  11. 2026-08-14 15:34 UTCGHSA enrichment
  12. 2026-08-14 03:19 UTCEG score recompute
  13. 2026-08-14 03:19 UTCGHSA enrichment
  14. 2026-08-13 21:59 UTCEPSS rescore
  15. 2026-08-13 06:01 UTCGHSA enrichment
  16. 2026-08-12 16:53 UTCEG score recompute
  17. 2026-08-12 16:53 UTCGHSA enrichment
  18. 2026-08-12 13:50 UTCEPSS rescore
  19. 2026-08-11 15:56 UTCEG score recompute
  20. 2026-08-11 15:55 UTCGHSA enrichment
  21. 2026-08-11 13:42 UTCEPSS rescore
  22. 2026-08-11 01:25 UTCEG score recompute
  23. 2026-08-11 01:25 UTCGHSA enrichment
  24. 2026-08-10 23:59 UTCEPSS rescore
  25. 2026-08-10 02:59 UTCGHSA enrichment
  26. 2026-08-09 14:44 UTCEG score recompute
  27. 2026-08-09 14:44 UTCGHSA enrichment
  28. 2026-08-09 13:46 UTCEPSS rescore
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-09 02:29 UTCEG score recompute
  31. 2026-08-09 02:29 UTCGHSA enrichment
  32. 2026-08-08 16:36 UTCEPSS rescore
  33. 2026-08-08 02:19 UTCEG score recompute
  34. 2026-08-08 02:19 UTCGHSA enrichment
  35. 2026-08-07 16:26 UTCEPSS rescore
  36. 2026-08-07 14:04 UTCGHSA enrichment
  37. 2026-08-07 01:49 UTCEG score recompute
  38. 2026-08-07 01:49 UTCGHSA enrichment
  39. 2026-08-06 13:46 UTCEPSS rescore
  40. 2026-08-06 10:29 UTCGHSA enrichment
  41. 2026-08-05 22:14 UTCEG score recompute
  42. 2026-08-05 22:14 UTCGHSA enrichment
  43. 2026-08-05 19:17 UTCEPSS rescore
  44. 2026-08-05 19:17 UTCEPSS rescore
  45. 2026-08-04 15:09 UTCEPSS rescore
  46. 2026-08-04 10:37 UTCEPSS rescore
  47. 2026-08-03 19:37 UTCEG score recompute
  48. 2026-08-03 19:37 UTCGHSA enrichment
  49. 2026-08-03 10:35 UTCEPSS rescore
  50. 2026-08-02 16:48 UTCGHSA enrichment
  51. 2026-08-02 04:32 UTCEG score recompute
  52. 2026-08-02 04:32 UTCGHSA enrichment
  53. 2026-08-02 02:26 UTCEPSS rescore
  54. 2026-08-01 04:15 UTCEPSS rescore
  55. 2026-07-30 16:27 UTCEPSS rescore
  56. 2026-07-30 01:30 UTCEPSS rescore
  57. 2026-07-28 15:35 UTCEPSS rescore
  58. 2026-07-27 14:12 UTCEPSS rescore
  59. 2026-07-26 14:54 UTCEPSS rescore
  60. 2026-07-26 14:54 UTCEPSS rescore
  61. 2026-07-25 14:17 UTCEPSS rescore
  62. 2026-07-23 14:18 UTCEPSS rescore
  63. 2026-07-23 14:18 UTCEPSS rescore
  64. 2026-07-23 03:01 UTCEG score recompute
  65. 2026-07-22 14:08 UTCEPSS rescore
  66. 2026-07-21 15:24 UTCEPSS rescore
  67. 2026-07-20 17:08 UTCEPSS rescore
  68. 2026-07-19 14:30 UTCEPSS rescore
  69. 2026-07-19 14:30 UTCEPSS rescore
  70. 2026-07-19 02:28 UTCEPSS rescore
  71. 2026-07-18 10:04 UTCEPSS rescore
  72. 2026-07-18 10:04 UTCEPSS rescore
  73. 2026-07-16 17:02 UTCEPSS rescore
  74. 2026-07-15 16:57 UTCEPSS rescore
  75. 2026-07-15 16:57 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-63705?
CVE-2025-63705 is a high vulnerability published on May 7, 2026. NPM package node-ts-ocr 1.0.15 is vulnerable to OS Command Injection via the invokeImageOcr function in src/index.js.
When was CVE-2025-63705 disclosed?
CVE-2025-63705 was first published in the National Vulnerability Database on May 7, 2026, with the most recent update on May 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-63705 actively exploited?
CVE-2025-63705 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 33.9% of all scored CVEs.
What is the CVSS score of CVE-2025-63705?
CVE-2025-63705 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2025-63705?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-63705, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-63705

Explore →

Is Your Infrastructure Affected by CVE-2025-63705?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs