EUVD-2026-42494
GHSA-mh32-g5q6-4x93
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Network-reachable with no authentication (PR:N), but user interaction required (UI:R); limited low-level CIA impact with no scope change, consistent with partial path traversal reach.
Primary rating from Vendor (vuldb).
CVSS VectorVendor: vuldb
Lifecycle Timeline
1DescriptionCVE.org
A security vulnerability has been detected in tumf mcp-text-editor up to 1.0.2. This issue affects the function _validate_file_path of the file mcp_text_editor/text_editor.py. Such manipulation of the argument file_path leads to path traversal. The attack can be launched remotely. The exploit has been disclosed publicly and may be used. The vendor closed the GitHub issue for this vulnerability without any explanation.
AnalysisAI
Path traversal in tumf mcp-text-editor up to version 1.0.2 allows remote attackers to read, write, or delete files outside the intended directory by supplying manipulated file path arguments to the _validate_file_path function in mcp_text_editor/text_editor.py. A public exploit has been disclosed (confirmed by VulDB and reflected in the CVSS 4.0 E:P modifier), and the vendor has closed the tracking GitHub issue without explanation, leaving the vulnerability unpatched. The CVSS 4.0 base score of 2.1 reflects limited confidentiality, integrity, and availability impact alongside a required user interaction step.
Technical ContextAI
CWE-22 (Path Traversal) arises when user-supplied file path input containing sequences such as ../ or absolute path references is not adequately sanitized before being used in filesystem operations. In this case, the function _validate_file_path within mcp_text_editor/text_editor.py is the designated validation boundary but fails to prevent directory escape. The product is an MCP (Model Context Protocol) server - a lightweight tool-server standard used to expose capabilities to LLM-based agents. Because MCP servers accept structured requests from AI orchestration layers that may relay externally-supplied data, path traversal flaws in this context can bridge trust boundaries between the AI agent and the underlying host filesystem. No CPE string was provided in the source data; affected scope is tumf/mcp-text-editor GitHub repository, versions up to and including 1.0.2.
RemediationAI
No vendor-released patch is identified at time of analysis - the vendor closed GitHub issue #22 (https://github.com/tumf/mcp-text-editor/issues/22) without comment or fix. Until a patched version is released, operators should consider the following specific compensating controls: restrict the MCP server's runtime user account to a tightly scoped chroot or container with an allowlist-based filesystem mount, so that even a successful traversal cannot reach sensitive paths (trade-off: operational complexity); implement an external request filter or middleware that rejects any file_path argument containing ../, absolute path prefixes, or null bytes before the request reaches the MCP tool (trade-off: requires custom instrumentation); or replace this tool with an alternative MCP text editor that has an active maintenance posture. Monitoring filesystem access logs for unexpected path patterns is advisable as a detective control. Consult https://vuldb.com/vuln/376953 for updated status.
Same weakness CWE-22 – Path Traversal
View allSame technique Path Traversal
View allShare
External POC / Exploit Code
Leaving vuln.today