# CVE-2025-68472: MindsDB has improper sanitation of filepath that leads to information disclosure and DOS

> Unauthenticated attackers can read arbitrary server files and cause denial of service via path traversal in the file upload API.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Jan 2026
- **Updated:** 20 Feb 2026
- **Also known as:** GHSA-qqhf-pm3j-96g7, PYSEC-2026-90

## What is CVE-2025-68472?

CVE-2025-68472 is a high-severity path traversal vulnerability in mindsdb, published on 12 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

MindsDB is a platform for building artificial intelligence from enterprise data. Prior to version 25.11.1, 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. 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". Only multipart uploads and URL-sourced uploads receive sanitization; JSON uploads lack any call to clear_filename or equivalent checks. This vulnerability is fixed in 25.11.1.

Weakness: CWE-36 (Absolute Path Traversal), CWE-23 (Relative Path Traversal), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-68472?

3 open source packages ship an affected version, including mindsdb and MindsDB. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mindsdb` | PyPI | All versions | 25.11.1 |
| `mindsdb` | PyPI | All versions | 25.11.1 |
| `MindsDB` | PyPI | All versions | 25.11.1 |

Products: Mindsdb Mindsdb.

## How do I fix CVE-2025-68472?

Upgrade mindsdb to 25.11.1 or later.

## Is CVE-2025-68472 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68472 exists.

Public exploit code:

- https://github.com/ExploreUnknowed/CVE-2025-68472 (github_poc): https://github.com/ExploreUnknowed/CVE-2025-68472

## Other vulnerabilities in mindsdb

- [CVE-2024-24759](https://insights.sbomify.com/CVE-2024-24759/): MindsDB Vulnerable to Bypass of SSRF Protection with DNS Rebinding (critical 9.3)
- [CVE-2023-50731](https://insights.sbomify.com/CVE-2023-50731/): MindsDB has arbitrary file write in file.py (critical 9.1)
- [CVE-2023-38699](https://insights.sbomify.com/CVE-2023-38699/): MindsDB 'Call to requests with verify=False disabling SSL certificate checks, security issue.' issue (critical 9.1)
- [CVE-2024-45856](https://insights.sbomify.com/CVE-2024-45856/): MindsDB Cross-site Scripting vulnerability (critical 9.0)
- [CVE-2026-27483](https://insights.sbomify.com/CVE-2026-27483/): MindsDB has Path Traversal in /api/files Leading to Remote Code Execution (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68472 and fix it if it is affected.

What it is: CVE-2025-68472 is a high-severity path traversal vulnerability in mindsdb, published on 12 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-68472 exists.

Affected packages and fixed versions:
- mindsdb (PyPI): affected all versions; fixed in 25.11.1
- mindsdb (PyPI): affected all versions; fixed in 25.11.1
- MindsDB (PyPI): affected all versions; fixed in 25.11.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68472/ (Markdown: https://insights.sbomify.com/CVE-2025-68472/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68472
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68472
- OSV: https://osv.dev/vulnerability/CVE-2025-68472

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68472/
Summaries are generated and may contain mistakes; the official description above is the record.