# CVE-2026-15138: tumf mcp-text-editor text_editor.py _validate_file_path path traversal

> Remote attackers can exploit a path traversal flaw in the tumf mcp-text-editor library to read or modify arbitrary files on the system.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Jul 2026
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-mh32-g5q6-4x93

## What is CVE-2026-15138?

CVE-2026-15138 is a medium-severity path traversal vulnerability in tumf mcp-text-editor, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-15138?


## How do I fix CVE-2026-15138?

No fix has been published for CVE-2026-15138 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-15138 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15138 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15138 and fix it if it is affected.

What it is: CVE-2026-15138 is a medium-severity path traversal vulnerability in tumf mcp-text-editor, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15138 exists.

Affected product: tumf mcp-text-editor. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15138/ (Markdown: https://insights.sbomify.com/CVE-2026-15138/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15138
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15138
- OSV: https://osv.dev/vulnerability/CVE-2026-15138

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15138/
Summaries are generated and may contain mistakes; the official description above is the record.