dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-15138

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable No privileges 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A path traversal vulnerability in the _validate_file_path function of mcp_text_editor/text_editor.py in tumf mcp-text-editor up to v1.0.2 allows remote attackers to access arbitrary files on the server by manipulating the file_path parameter with directory traversal sequences (e.g., ../../). The validation function fails to properly sanitize or canonicalize path inputs.

MitigationImplement proper path validation by canonicalizing the resolved path and verifying it stays within an allowed base directory, rejecting any input containing traversal sequences like '..' that escape the intended scope.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if mcp-text-editor is installed
    Locate the tumf mcp-text-editor package in your environment - check your Python packages, project dependencies, or node_modules if JavaScript. Look for a directory or package named 'mcp_text_editor' containing 'text_editor.py'.
    Affected if The package is present in your environment
  2. Determine the installed version
    Run a package manager command to query the installed version of mcp-text-editor, such as 'pip show mcp-text-editor' or check your lockfile/package.json for the version number.
    Affected if The installed version is v1.0.2 or earlier (any version up to and including v1.0.2)
  3. Verify the vulnerable function exists
    Locate the file 'mcp_text_editor/text_editor.py' in the installed package and search for the function named '_validate_file_path'. Confirm it exists in your environment.
    Affected if The _validate_file_path function is present in your copy of text_editor.py
  4. Inspect the validation logic
    Open mcp_text_editor/text_editor.py and examine the _validate_file_path function. Look for whether it performs path canonicalization (e.g., using os.path.realpath or pathlib.Path.resolve) and whether it validates the resolved path stays within an allowed base directory.
    Affected if The function does NOT canonicalize paths or does NOT verify the resolved path stays within an allowed base directory, allowing '..' sequences to pass through
  5. Check if the editor service is network-exposed
    Determine whether the mcp-text-editor service is accessible over a network or exposed via an API endpoint that accepts file_path parameters from remote clients.
    Affected if The service accepts file_path input from remote or untrusted sources over a network
  6. Review access logs for traversal attempts
    Examine server or application logs for requests containing '../' or '..\' patterns in file_path parameters, which would indicate exploitation attempts.
    Affected if You observe directory traversal patterns in your logs (indicates active scanning or exploitation)

You are affected if the mcp-text-editor package (v1.0.2 or earlier) with the vulnerable _validate_file_path function is installed and accessible, and the service accepts file_path input that could contain traversal sequences.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper path validation by canonicalizing the resolved path and verifying it stays within an allowed base directory, rejecting any input containing traversal sequences like '..' that escape the intended scope.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15138 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15138 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data