LiveActive security incident?Get immediate response
CVE Record

CVE-2026-27483: MindsDB has Path Traversal in /api/files Leading to Remote Code Execution

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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

MindsDB versions before 25.9.1.1 let a logged-in attacker abuse file upload handling to write files outside the intended location. The advisory states this can lead to remote command execution. Organizations running MindsDB should treat this as urgent because compromise could affect data-connected AI systems and the server hosting MindsDB.

Executive priority

Prioritize remediation quickly for any production MindsDB instance, especially if exposed beyond a small trusted administrator group. This is high severity because authenticated misuse may become server compromise. If MindsDB is not deployed, document non-exposure and monitor vendor advisories.

Technical view

CVE-2026-27483 is a CWE-22 path traversal in MindsDB’s /api/files Upload File endpoint. Multipart upload filename handling allowed traversal sequences and arbitrary content to be written before filename cleanup routines were applied. The issue affects MindsDB versions earlier than 25.9.1.1 and has CVSS 8.8, requiring network access and low privileges.

Likely exposure

Exposure is most likely where MindsDB is deployed below version 25.9.1.1 and authenticated users can access the /api/files upload API. Internet-facing or broadly accessible deployments carry higher operational risk. The sources do not identify affected managed services or downstream products beyond MindsDB itself.

Exploitation context

The public advisory states an authenticated attacker can exploit this issue to achieve remote command execution. The provided data does not show CISA KEV listing or cited evidence of active exploitation. Do not assume exploitation in the wild without additional telemetry or vendor updates.

Researcher notes

The core issue is unsafe filename/path handling during multipart upload, with file write occurring before sanitization. Public sources identify the patch release and fixing commit, but do not provide evidence of active exploitation. Validation should focus on version confirmation, endpoint access, and signs of unexpected file writes.

Mitigation direction

  • Upgrade MindsDB to version 25.9.1.1 or later.
  • Review the GitHub security advisory for vendor-specific guidance.
  • Restrict access to MindsDB and the /api/files endpoint to trusted users.
  • Audit MindsDB accounts and remove unnecessary upload privileges.
  • Investigate suspicious file uploads or unexpected server-side file changes.

Validation and detection

  • Inventory all MindsDB deployments and record their versions.
  • Confirm no deployment is running a version earlier than 25.9.1.1.
  • Verify authentication and network controls protect /api/files.
  • Review logs for unusual upload activity or traversal-like filenames.
  • Confirm the vendor patch is applied in build and runtime environments.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-27483 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-27483Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
mindsdbmindsdb< 25.9.1.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.