Handwriting-OCR handwriting-ocr-mcp-server 0.1.0 upload_document src/index.ts fs.readFileSync File path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 2.43 |
Summary
A vulnerability, which was classified as critical, was found in Handwriting-OCR handwriting-ocr-mcp-server 0.1.0. Affected by this issue is the function fs.readFileSync of the file src/index.ts of the component upload_document. Executing a manipulation of the argument File can lead to path traversal.
This vulnerability is handled as CVE-2026-19372. It is possible to launch the attack on the local host. Additionally, an exploit exists.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability has been found in Handwriting-OCR handwriting-ocr-mcp-server 0.1.0 and classified as critical. This vulnerability affects the function fs.readFileSync of the file src/index.ts of the component upload_document. The manipulation of the argument file with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-19372. The exploitation appears to be easy. The attack needs to be approached locally. Technical details and also a exploit are known. The MITRE ATT&CK project declares the attack technique as T1006.
It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Path traversalCWE: CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Proof-of-Concept
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
08/09/2026 Advisory disclosed08/09/2026 VulDB entry created
08/09/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Not defined
CVE: CVE-2026-19372 (🔒)
GCVE (CVE): GCVE-0-2026-19372
GCVE (VulDB): GCVE-100-387256
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 08/09/2026 09:30Changes: 08/09/2026 09:30 (58)
Complete: 🔍
Submitter: gongyanyu05
Cache ID: 216::103
Submit
Accepted
- Submit #866270: Handwriting-OCR handwriting-ocr-mcp-server 0.1.0 Path Traversal (by gongyanyu05)
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.