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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

EPSS

• CVE-2025-68472: 20.26% estimated exploitation activity in the next 30 days; percentile 97.47 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 sourcetype is not "url": - data = request.json (line ~104) accepts attacker input without validation. - filepath = os.path.join(tempdirpath, 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 tempdirpath and targets the attacker-specified location. - The resulting path is handed to ca.filecontroller.savefile(...), which wraps FileReader(path=sourcepath) (mindsdb/interfaces/file/filecontroller.py:66), causing the application to read the contents of that arbitrary file. The subsequent shutil.move(filepath, ...) call also relocates the victim file into…

Published by the source

12 Jan 2026, 16:10 UTC

Last modified by the source

6 Jun 2026, 00:45 UTC

Source last checked

26 Oct 2026, 13:44 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-qqhf-pm3j-96g7

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-qqhf-pm3j-96g7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-68472

Advisory: MindsDB has improper sanitation of filepath that leads to information disclosure and DOS
IDs: CVE-2025-68472, GHSA-qqhf-pm3j-96g7
Record: https://patchnext.com/advisories/cve-2025-68472 (revision 2, source checked 26 Oct 2026, 13:44 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mindsdb 25.11.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mindsdb: affected < 25.11.1; fixed in 25.11.1

## Suggested inspection (read-only)
- `python -m pip show mindsdb`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mindsdb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-qqhf-pm3j-96g7 (OSV record GHSA-qqhf-pm3j-96g7 lists affected ranges: PyPI mindsdb >=0 <25.11.1 (fixed))
- Verified: https://github.com/advisories/GHSA-qqhf-pm3j-96g7 (GitHub-reviewed advisory GHSA-qqhf-pm3j-96g7 lists affected ranges: PyPI mindsdb >=0 <25.11.1)

Commands are suggestions: review each one before running it.