Skip to main content

mcp-file-analyzer CVE-2026-94037

| EUVDEUVD-2026-83753 LOW
Path Traversal (CWE-22)
2026-09-20 VulDB GHSA-882h-38q7-cgpc
2.1
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach exposed MCP analyze_csv_data tool
  2. Delivery
    Supply traversal filename argument (../../)
  3. Exploit
    Bypass directory restriction in main.py
  4. Execution
    Read arbitrary host file
  5. Impact
    Exfiltrate sensitive data

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK

2 techniques across 2 tactics: Discovery, Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a reachable instance of the 00Kisumi00 mcp-file-analyzer MCP server and the ability to invoke its analyze_csv_data tool with an attacker-controlled 'filename' argument (PR:L - an MCP client/agent connection is needed, so it is not fully anonymous). No user interaction and no non-default configuration are required beyond running the tool. Exploitation is limited by the product's near-zero deployment: it is a rolling-release hobby project with no published releases and an unresponsive maintainer, so there is no fixed version to pin and no vendor patch.

Impact

This is a genuine but low-severity path traversal (CWE-22) in an obscure open-source MCP tool. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) indicates network-reachable, low-complexity exploitation requiring only low privilege (an actor able to invoke the MCP tool). The E:P (Proof-of-Concept) exploit maturity aligns with the confirmed public POC in the project's own GitHub issue tracker, so exploitation is 'publicly available exploit code exists' - but NOT KEV-listed and no active exploitation is claimed. No EPSS score is provided; given the tiny, single-author hobby-project footprint, real-world exploitation is likely to be negligible/opportunistic rather than widespread. The vendor scores confidentiality impact as VC:L; I dispute this - an unsanitized filename argument reaching a file-reading routine typically enables arbitrary file disclosure (VC:H), which would raise the score. Net: real vulnerability with a public POC, but the negligible deployment base and unresponsive maintainer make this a low operational priority for most defenders, not a high-CVSS-but-low-real-risk enterprise concern.

Exploit ScenarioDerived

An actor with the ability to send requests to (or drive an AI agent connected to) the mcp-file-analyzer server invokes the analyze_csv_data tool with a filename such as '../../../../etc/passwd'. The unsanitized path escapes the intended data directory, causing the tool to read and return the contents of an arbitrary file on the host. A public proof-of-concept exists in the project's GitHub issue #1.

Monitor Track and reassess. Why: LOW severity (CVSS 0.1-3.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 20, 2026

Path traversal (CWE-22) in the 00Kisumi00 mcp-file-analyzer MCP tool allows authenticated remote attackers to read arbitrary files by supplying a crafted filename to the analyze_csv_data function implemented in main.py's ControlFlowNode. Publicly available exploit code exists, but the vulnerability is low severity (CVSS 5.3; assessed CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) and the project is a rolling-release hobby tool with near-zero deployment. No vendor patch has been released and the maintainer has not responded to the issue report.

RemediationAI

No vendor-released patch identified at time of analysis. Because the project is a rolling-release hobby tool with an unresponsive maintainer, users should apply compensating controls: restrict access to the MCP server to trusted clients only (reduces exposure but may limit legitimate agent functionality); implement input validation to reject filenames containing '../' or absolute paths before passing them to analyze_csv_data (may break legitimate file analysis if not carefully whitelisted); run the MCP server with least privilege in a sandboxed environment to limit the impact of arbitrary file reads; and disable the analyze_csv_data tool if it is not needed. Advisory references include https://github.com/00Kisumi00/mcp-file-analyzer/issues/1 and https://vuldb.com/vuln/407966.

Affected VersionsENISA

mcp-file-analyzer 84740852f0cf0cf5db4781b1ca6d7c6a6d210405

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

mcp-file-analyzer is a rolling-release hobby project that exposes an MCP (Model Context Protocol) server; MCP is an open standard that lets AI assistants call external tools. The vulnerability lies in the analyze_csv_data tool, specifically in the ControlFlowNode function of main.py, where the filename argument is not sanitized before file access. This is a classic CWE-22 path traversal: an attacker can use sequences like '../' to read files outside the intended directory. The CPE cpe:2.3:a:00kisumi00:mcp-file-analyzer:*:*:*:*:*:*:*:* confirms the affected package and its wildcarded version, reflecting the project's rolling-release model with no fixed versions. The assessed impact is limited to confidentiality (C:H) with no integrity (I:N) or availability (A:N) impact, and exploitation requires an MCP client connection (PR:L).

Know when Mcp File Analyzer gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.1 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P
vuln.today AI 6.5 MEDIUM

Network-reachable low-complexity traversal invocable by a low-privileged MCP client (PR:L); arbitrary file read is confidentiality-only, so I set C:H (disputing vendor VC:L) with I/A none.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
None
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Severity Changed
Sep 20, 2026 - 17:22 NVD
MEDIUM LOW
CVSS changed
Sep 20, 2026 - 17:22 NVD
5.3 (MEDIUM) 2.1 (LOW)
CVE Published
Sep 20, 2026 - 16:15 cve.org
MEDIUM 5.3

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.3%
Top 74% exploitable
Prevalence
Rare
obscure single-author hobby MCP project, no enterprise footprint
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
LOW severity (CVSS 0.1-3.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy