CVE-2026-7213

7.3

ef10007 · MLOps_MCP

A path traversal vulnerability in the MLOps_MCP save_file tool allows remote attackers to manipulate file destinations via the filename argument.

Executive summary

A remote path traversal vulnerability in ef10007 MLOps_MCP version 1.0.0 poses a security risk by allowing unauthorized file system access.

Vulnerability

This is a path traversal vulnerability (CWE-22) located in the fastmcp_server.py file within the save_file tool. The vulnerability is exploitable by unauthenticated remote attackers through the manipulation of the filename or destination arguments.

Business impact

The vulnerability allows an attacker to manipulate file paths, potentially resulting in unauthorized file access or modification. Given the CVSS score of 7.3, this represents a significant risk to the integrity and availability of the affected system. Successful exploitation could lead to data exposure or system instability, impacting the reliability of the MLOps pipeline.

Remediation

Immediate Action: Since no official patch is currently available, users should restrict network access to the affected service to prevent remote exploitation.

Proactive Monitoring: Review system and application logs for suspicious file path patterns or unauthorized attempts to access directories outside of the intended scope.

Compensating Controls: Implement Web Application Firewall (WAF) rules designed to detect and block directory traversal sequences, such as dot-dot-slash patterns, in incoming requests.

Exploitation status

Public Exploit Available: Yes, a public proof-of-concept exists, as documented in the project's GitHub issue tracker (https://github.com/ef10007/MLOps_MCP/issues/1).

Analyst recommendation

Given the confirmed existence of a public proof-of-concept and the lack of a vendor-provided patch, this vulnerability should be treated with high priority. Organizations utilizing MLOps_MCP should immediately isolate the affected component from the public internet and implement strict access controls to mitigate the risk of unauthorized file system interaction.

Sources

Originally found and disclosed by SmallW (VulDB User), with VulDB CNA Team (coordinator), per the CVE Program record.