CVE-2026-94037

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 4.3Exploit: Elevated riskExposed services: Not assessed

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

A weakness has been identified in 00Kisumi00 mcp-file-analyzer up to 84740852f0cf0cf5db4781b1ca6d7c6a6d210405. This affects the function ControlFlowNode of the file main.py of the component analyze_csv_data MCP tool. This manipulation of the argument filename causes path traversal. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. The project was informed of the problem early through an issue report but has not responded yet.

CVSS v3
4.3
EG Score
4.3MEDIUMhigh confidence
EG Risk
35
EG Risk 35/100CISA SSVC

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
Severity43% × 45%
Exploitation40% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
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
38th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 20, 2026

Last Modified

September 22, 2026

Advisory Details (2)

Auto-updated Sep 20, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

GitHub - 00Kisumi00/mcp-file-analyzer · GitHub

https://github.com/00Kisumi00/mcp-file-analyzer/
generic🟡 PoC Available

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in mcp-file-analyzer · Issue #1 · 00Kisumi00/mcp-file-analyzer · GitHub

https://github.com/00Kisumi00/mcp-file-analyzer/issues/1

Vendor Advisories for CVE-2026-94037(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 19× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-10-04 23:23 UTCEPSS rescore
  2. 2026-10-04 16:20 UTCEG score recompute
  3. 2026-10-04 16:20 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 14:16 UTCEG score recompute
  6. 2026-10-03 14:16 UTCGHSA enrichment
  7. 2026-10-02 17:57 UTCEPSS rescore
  8. 2026-10-02 12:13 UTCEG score recompute
  9. 2026-10-02 12:12 UTCGHSA enrichment
  10. 2026-10-01 19:51 UTCEPSS rescore
  11. 2026-10-01 09:50 UTCEG score recompute
  12. 2026-10-01 09:50 UTCGHSA enrichment
  13. 2026-09-30 15:04 UTCEPSS rescore
  14. 2026-09-30 07:48 UTCEG score recompute
  15. 2026-09-30 07:48 UTCGHSA enrichment
  16. 2026-09-29 05:44 UTCEG score recompute
  17. 2026-09-29 05:44 UTCGHSA enrichment
  18. 2026-09-28 13:52 UTCEPSS rescore
  19. 2026-09-28 13:52 UTCEPSS rescore
  20. 2026-09-28 03:42 UTCEG score recompute
  21. 2026-09-28 03:42 UTCGHSA enrichment
  22. 2026-09-27 13:49 UTCEPSS rescore
  23. 2026-09-27 01:39 UTCEG score recompute
  24. 2026-09-27 01:39 UTCGHSA enrichment
  25. 2026-09-26 15:59 UTCEPSS rescore
Show 21 more
  1. 2026-09-25 23:35 UTCGHSA enrichment
  2. 2026-09-24 21:29 UTCEG score recompute
  3. 2026-09-24 21:29 UTCGHSA enrichment
  4. 2026-09-24 14:04 UTCEPSS rescore
  5. 2026-09-23 19:08 UTCEG score recompute
  6. 2026-09-23 19:08 UTCGHSA enrichment
  7. 2026-09-23 17:54 UTCEPSS rescore
  8. 2026-09-22 16:22 UTCEG score recompute
  9. 2026-09-22 16:22 UTCGHSA enrichment
  10. 2026-09-22 16:19 UTCNVD updateCVSS v4 → 2.1
  11. 2026-09-22 16:01 UTCEPSS rescore
  12. 2026-09-22 15:44 UTCMITRE cvelistV5CVSS v4 → 5.3
  13. 2026-09-22 15:43 UTCEG score recompute
  14. 2026-09-22 15:43 UTCGHSA enrichment
  15. 2026-09-21 21:09 UTCEPSS rescore
  16. 2026-09-21 13:40 UTCEG score recompute
  17. 2026-09-21 13:40 UTCGHSA enrichment
  18. 2026-09-20 17:17 UTCEG score recompute
  19. 2026-09-20 17:17 UTCNVD updateCVSS v4 → 2.1
  20. 2026-09-20 16:26 UTCEG score recompute
  21. 2026-09-20 16:26 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-94037?
CVE-2026-94037 is a medium vulnerability published on September 20, 2026. A weakness has been identified in 00Kisumi00 mcp-file-analyzer up to 84740852f0cf0cf5db4781b1ca6d7c6a6d210405. This affects the function ControlFlowNode of the file main.py of the component analyzecsvdata MCP tool. This manipulation of the argument filename causes path traversal. Remote…
When was CVE-2026-94037 disclosed?
CVE-2026-94037 was first published on September 20, 2026, with the most recent update on September 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-94037 actively exploited?
CVE-2026-94037 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-94037?
CVE-2026-94037 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-94037?
No fix for CVE-2026-94037 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 vendor advisories EchelonGraph has for CVE-2026-94037 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-94037?

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

Book a Demo →Browse All CVEs