CVE-2026-15138

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-07-09. A secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
6.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.3Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's description, written by its CNA (VulDB), states the affected versions: "A security vulnerability has been detected in tumf mcp-text-editor up to 1.0.2." No release containing a fix is confirmed on record.

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.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
42nd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 9, 2026

Last Modified

July 9, 2026

Advisory Details (2)

Auto-updated Jul 9, 2026
No fix on record yet.
Web page

[Security] "Arbitrary file read/write: path validation is a single "".."" substring check with no directory confinement" · Issue #22 · tumf/mcp-text-editor · GitHub

https://github.com/tumf/mcp-text-editor/issues/22
Web page

GitHub - tumf/mcp-text-editor · GitHub

https://github.com/tumf/mcp-text-editor/

Vendor Advisories for CVE-2026-15138(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 182 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 82 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-12 16:32 UTCEG score recompute
  5. 2026-10-11 20:10 UTCEG score recompute
  6. 2026-10-11 17:22 UTCEG score recompute
  7. 2026-10-11 14:55 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  14. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  18. 2026-10-01 16:06 UTCEG score recompute
  19. 2026-10-01 16:06 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  20. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-09-28 11:08 UTCEG score recompute
  24. 2026-09-28 11:08 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  25. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
Show 75 more
  1. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-09-24 11:43 UTCEG score recompute
  3. 2026-09-24 11:43 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  4. 2026-09-23 06:01 UTCEG score recompute
  5. 2026-09-23 06:01 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  6. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  7. 2026-09-18 05:39 UTCEG score recompute
  8. 2026-09-18 05:39 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  9. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  10. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-09-14 08:30 UTCEG score recompute
  12. 2026-09-14 08:30 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  13. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  14. 2026-09-13 08:21 UTCEG score recompute
  15. 2026-09-13 08:21 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  16. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  17. 2026-09-12 03:28 UTCEG score recompute
  18. 2026-09-12 03:28 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  19. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  20. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  24. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-09-05 22:38 UTCEG score recompute
  26. 2026-09-05 22:38 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  27. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  28. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  29. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  30. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  31. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  32. 2026-08-30 06:59 UTCEG score recompute
  33. 2026-08-30 06:59 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  34. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  35. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  36. 2026-08-27 21:47 UTCEG score recompute
  37. 2026-08-27 21:47 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  38. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  39. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  40. 2026-08-26 04:42 UTCEG score recompute
  41. 2026-08-26 04:42 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  42. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  43. 2026-08-25 04:10 UTCEG score recompute
  44. 2026-08-25 04:10 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  45. 2026-08-24 03:59 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  46. 2026-08-23 03:49 UTCEG score recompute
  47. 2026-08-23 03:49 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  48. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  49. 2026-08-22 03:40 UTCEG score recompute
  50. 2026-08-22 03:40 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  51. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  52. 2026-08-21 02:04 UTCEG score recompute
  53. 2026-08-21 02:04 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  54. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  55. 2026-08-20 01:53 UTCEG score recompute
  56. 2026-08-20 01:53 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  57. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  58. 2026-08-18 22:27 UTCEG score recompute
  59. 2026-08-18 22:27 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  60. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  61. 2026-08-17 22:18 UTCEG score recompute
  62. 2026-08-17 22:18 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  63. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  64. 2026-08-16 18:09 UTCEG score recompute
  65. 2026-08-16 18:09 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  66. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  67. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  68. 2026-08-15 18:00 UTCEG score recompute
  69. 2026-08-15 18:00 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  70. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  71. 2026-08-14 17:50 UTCEG score recompute
  72. 2026-08-14 17:50 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  73. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  74. 2026-08-13 17:24 UTCGHSA enrichmentGHSA-mh32-g5q6-4x93 · GitHub severity LOW · GitHub CVSS 6.3
  75. 2026-08-12 17:08 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-15138?
CVE-2026-15138 is a medium-severity vulnerability; its CVE record was published on July 9, 2026. A security vulnerability has been detected in tumf mcp-text-editor up to 1.0.2. This issue affects the function validatefilepath of the file mcptexteditor/texteditor.py. Such manipulation of the argument file_path leads to path traversal. The attack can be launched remotely. The exploit has been…
When was the CVE record for CVE-2026-15138 published?
The CVE record for CVE-2026-15138 was published on July 9, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 9, 2026; the record at its source may have been updated since.
Is CVE-2026-15138 actively exploited?
CVE-2026-15138 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (42nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15138?
CVE-2026-15138 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15138?
No fix for CVE-2026-15138 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's description, written by its CNA (VulDB), states the affected versions: "A security vulnerability has been detected in tumf mcp-text-editor up to 1.0.2." No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-15138 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-15138

Explore →

Is Your Infrastructure Affected by CVE-2026-15138?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs