CVE-2025-68472

MindsDB versions prior to 25.11.1 contain an unauthenticated path traversal vulnerability (CWE-22) in the file upload API: the PUT handler in file.py joins user-controlled JSON fields directly into a filesystem path when the request body is JSON and source_type is not "url". Unlike multipart and URL-sourced uploads, JSON uploads receive no sanitization such as a clear_filename check, so traversal sequences in the supplied name are resolved without validation. A remote, unauthenticated attacker can read arbitrary files from the server filesystem and have them moved into MindsDB's storage, exposing sensitive data such as configuration files and credentials; the CVSS 9.1 (critical) score reflects high confidentiality and availability impact. Any MindsDB deployment before 25.11.1 that exposes the file upload API over the network without authentication is affected. A public advisory and PoC reference exist (GHSA-qqhf-pm3j-96g7), EPSS estimates a 20.3% probability of exploitation within 30 days (97th percentile), but the issue is not on CISA KEV and no confirmed in-the-wild exploitation is reported in the available data.

What to do: Upgrade to MindsDB 25.11.1 or later, which adds sanitization for JSON file uploads. Until patched, restrict network access to the file upload API (PUT endpoint in file.py) and require authentication or reverse-proxy filtering on the filename/JSON body fields. Check MindsDB storage and server logs for signs of unexpected files moved into storage or reads of sensitive paths (e.g., configuration or credential files) via crafted upload requests.