tumf mcp-text-editor up to 1.0.2 text_editor.py _validate_file_path path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 1.73+ |
Summary
A vulnerability has been found in tumf mcp-text-editor up to 1.0.2 and classified as critical. Impacted is the function _validate_file_path of the file mcp_text_editor/text_editor.py. Performing a manipulation of the argument file_path results in path traversal.
This vulnerability was named CVE-2026-15138. The attack may be initiated remotely. In addition, an exploit is available.
The vendor closed the GitHub issue for this vulnerability without any explanation.
Details
A vulnerability was found in tumf mcp-text-editor up to 1.0.2. It has been classified as critical. This affects the function _validate_file_path of the file mcp_text_editor/text_editor.py. The manipulation of the argument file_path with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-15138. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1006 for this issue.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The vendor closed the GitHub issue for this vulnerability without any explanation.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
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: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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
07/08/2026 Advisory disclosed07/08/2026 VulDB entry created
07/08/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 22
Status: Not defined
CVE: CVE-2026-15138 (🔒)
GCVE (CVE): GCVE-0-2026-15138
GCVE (VulDB): GCVE-100-376953
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/08/2026 19:21Changes: 07/08/2026 19:21 (59)
Complete: 🔍
Submitter: geochen
Cache ID: 216::103
Submit
Accepted
- Submit #851188: Tumf mcp-text-editor 1.0.2 Path Traversal (by geochen)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.