Critical File handling exploit reference

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

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.

Published Jan 12, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: GitHub_M

Moderate

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

EPSS 20.3% (30-day exploitation probability)+15
Technical severity (critical)+10
CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

20.26%

ahead of 97% of scored CVEs · Oct 14, 2026

Affects

Mindsdb

CVSS base

9.1

Critical · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

Proof of concept

none · proof-of-concept · active

Automatable

can an attacker script the kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Mindsdb Mindsdb).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Mindsdb	Mindsdb	< 25.11.1	Vulnerable	NIST National Vulnerability Database
Mindsdb	Mindsdb	version < 25.11.1	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
9.1	CVSS 3.1	Critical	3.9	5.2	nvd@nist.gov via NIST National Vulnerability Database
8.1	CVSS 3.1	High	2.8	5.2	security-advisories@github.com via NIST National Vulnerability Database
8.1	CVSS 3.1	High	—	—	GitHub_M via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H (score shown at the top: nvd@nist.gov)

Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 9.1 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-22 · Path Traversal

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 20.26%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Monitor file creation in web directories and paths with traversal sequences (../).

web/proxy/WAF logsnetwork IDS/IPSfile integrity (FIM)endpoint telemetry (EDR)

Timeline

What happened to this CVE, newest first.

2026
Affected products added · mindsdb/mindsdb
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 13, 2026
CVSS changed · 9.1
Oct 13, 2026 · NIST National Vulnerability Database
Source status changed · → Modified
Oct 13, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 13, 2026 · NIST National Vulnerability Database
CVE published
Jan 12, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

2 on the record

github.com/mindsdb/mindsdb/security/advisories/GHSA-qqhf-pm3j-96g7
Exploit, Vendor Advisory, x_refsource_CONFIRM, NIST National Vulnerability Database
www.bluerock.io/post/cve-2025-68472-mindsdb-file-upload-path-traversal
NIST National Vulnerability Database

Elsewhere on this site

Mindsdb
every CVE for this vendor

File handling
same class

CWE-22
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-86173 MindsDB through 26.1.0 Unauthenticated SSRF via Web Crawler Sep 5, 2026
High CVE-2026-27483 MindsDB has Path Traversal in /api/files Leading to Remote Code Execution Feb 24, 2026
High CVE-2026-2531 MindsDB File Upload security.py clear_filename server-side request forgery Feb 16, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-68472 is "MindsDB has improper sanitation of filepath that leads to information disclosure and DOS", rated Critical. It affects Mindsdb (Mindsdb); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.1 describes technical severity. EPSS 20.26% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.