CVE-2026-27483
Received Received - Intake
Path Traversal in MindsDB /api/files Enables Remote Code Execution

Publication date: 2026-02-24

Last updated on: 2026-02-26

Assigner: GitHub, Inc.

Description
MindsDB is a platform for building artificial intelligence from enterprise data. Prior to version 25.9.1.1, there is a path traversal vulnerability in Mindsdb's /api/files interface, which an authenticated attacker can exploit to achieve remote command execution. The vulnerability exists in the "Upload File" module, which corresponds to the API endpoint /api/files. Since the multipart file upload does not perform security checks on the uploaded file path, an attacker can perform path traversal by using `../` sequences in the filename field. The file write operation occurs before calling clear_filename and save_file, meaning there is no filtering of filenames or file types, allowing arbitrary content to be written to any path on the server. Version 25.9.1.1 patches the issue.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-24
Last Modified
2026-02-26
Generated
2026-05-07
AI Q&A
2026-02-24
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
mindsdb mindsdb to 25.9.1.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

[{'type': 'paragraph', 'content': "CVE-2026-27483 is a path traversal vulnerability in MindsDB's /api/files interface that affects versions prior to 25.9.1.1. The issue exists in the file upload module where the filename parameter is not properly sanitized, allowing an authenticated attacker to include '../' sequences in the filename. This enables the attacker to write files to arbitrary locations on the server, outside the intended directory."}, {'type': 'paragraph', 'content': 'Because the file write operation happens before any filename cleaning or saving logic, there is no filtering of filenames or file types, which allows arbitrary content to be written anywhere on the server. This can be exploited to overwrite critical files and achieve remote command execution.'}] [3]


How can this vulnerability impact me? :

[{'type': 'paragraph', 'content': 'This vulnerability can have severe impacts including remote code execution (RCE) on the server hosting MindsDB. An attacker with authentication can exploit the path traversal flaw to overwrite important executable files, such as Python package files used by the system.'}, {'type': 'paragraph', 'content': "For example, by overwriting the pip package's __init__.py file with malicious code, the attacker can execute arbitrary commands when pip is invoked, effectively gaining control over the server."}, {'type': 'paragraph', 'content': 'The vulnerability has a high CVSS score of 8.8, indicating high impact on confidentiality, integrity, and availability of the system.'}] [3]


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

[{'type': 'paragraph', 'content': 'This vulnerability can be detected by monitoring for suspicious or unauthorized file upload attempts to the /api/files endpoint, especially those containing path traversal sequences such as "../" in the filename field.'}, {'type': 'paragraph', 'content': 'Since the vulnerability requires authentication, reviewing authenticated API requests to /api/files for filenames with directory traversal patterns is critical.'}, {'type': 'paragraph', 'content': 'Network detection can involve inspecting HTTP PUT requests to /api/files for multipart/form-data uploads with filenames containing "../" sequences.'}, {'type': 'list_item', 'content': "Use web server or application logs to search for suspicious filenames: grep -r '\\.\\./' /path/to/mindsdb/logs"}, {'type': 'list_item', 'content': 'Capture and analyze network traffic for PUT requests to /api/files with suspicious filenames using tools like tcpdump or Wireshark.'}, {'type': 'list_item', 'content': "Example command to search logs for path traversal attempts: grep -i 'PUT /api/files' /var/log/mindsdb/access.log | grep '\\.\\./'"}, {'type': 'list_item', 'content': 'Check for unexpected file modifications or creations outside the intended upload directory, especially in critical system paths.'}] [3]


What immediate steps should I take to mitigate this vulnerability?

The primary mitigation step is to upgrade MindsDB to version 25.9.1.1 or later, where the vulnerability has been patched.

The patch includes validation and sanitization of uploaded filenames to prevent path traversal, improved file handling, and stricter multipart form parsing.

Until the upgrade can be applied, restrict access to the /api/files endpoint to trusted authenticated users only, and monitor for suspicious upload activity.

Consider implementing additional application-level controls to validate and sanitize filenames before processing uploads.

Review and restrict permissions on directories where files are uploaded to minimize potential damage from arbitrary file writes.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart