CVE-2026-27483: Mindsdb path traversal (CVSS 8.8)

Description

MindsDB is a platform for building artificial intelligence from enterprise data. Prior to version 25.9.1.1, there is a path traversal vulnerability in Mindsdb's /api/files interface, which an authenticated attacker can exploit to achieve remote command execution. The vulnerability exists in the "Upload File" module, which corresponds to the API endpoint /api/files. Since the multipart file upload does not perform security checks on the uploaded file path, an attacker can perform path traversal by using `../` sequences in the filename field. The file write operation occurs before calling clear_filename and save_file, meaning there is no filtering of filenames or file types, allowing arbitrary content to be written to any path on the server. Version 25.9.1.1 patches the issue.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredLow

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

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

Affected products

Mindsdb< 25.9.1.1

Remediation

Fixed in

Mindsdb≥ 25.9.1.1

Patch & vendor advisories

References

https://github.com/mindsdb/mindsdb/commit/87a44bdb2b97f963e18f10a068e1a1e2690505efPatch
https://github.com/mindsdb/mindsdb/releases/tag/v25.9.1.1ProductRelease Notes
https://github.com/mindsdb/mindsdb/security/advisories/GHSA-4894-xqv6-vrfqExploitVendor Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-27483 being actively exploited?

CVE-2026-27483 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 8.82%.

How severe is CVE-2026-27483?

CVE-2026-27483 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 8.82% probability of exploitation.

Which products are affected by CVE-2026-27483?

Affected products include Mindsdb.

How do I fix CVE-2026-27483?

Upgrade affected software to a fixed version, for example Mindsdb 25.9.1.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-27483 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo