Skip to content

GHSA-9f6m-65v9-x9g2 CVE-2026-7711 PYSEC-2026-2648

MindsDB has an Improper Access Control Issue

High PyPI
Severity
0.0 / 10
High · CVSS 4.0
Exploit chance (EPSS)
0.28%
Chance of exploitation in the next 30 days. Higher than 20.96% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
None yet
No fixed version published

Description

A weakness has been identified in MindsDB up to 26.01. This impacts the function exec of the file mindsdb/integrations/handlers/byom_handler/proc_wrapper.py of the component Engine Handler. Executing a manipulation can lead to unrestricted upload. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Affected versions

PyPI

PackageVulnerableFixed in
mindsdb
<= 26.0.1
No fix yet

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Attack vector
Network
Attack complexity
Low
Attack requirements
None
Privileges required
None
User interaction
None
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
Low
Availability (vulnerable system)
Low
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None
Exploit maturity
Proof of concept

CVSS 3.1 7.3

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

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-4894-xqv6-vrfq
MindsDB: Path Traversal in /api/files Leading to Remote Code Execution
High Also affects mindsdb
GHSA-6xw9-2p64-7622
MindsDB affected by a SSRF vulnerability
High Also affects mindsdb
GHSA-qqhf-pm3j-96g7
MindsDB has improper sanitation of filepath that leads to information disclosure and DOS
Critical Also affects mindsdb
GHSA-32fj-r8qw-r8w8
MindsDB Cross-site Scripting vulnerability
Medium Also affects mindsdb
GHSA-crmg-rp64-5cm3
MindsDB Eval Injection vulnerability
High Also affects mindsdb
GHSA-wf9g-c67g-h4ch
MindsDB Eval Injection vulnerability
High Also affects mindsdb
GHSA-wcjw-3v6p-4v3r
MindsDB Eval Injection vulnerability
High Also affects mindsdb
GHSA-v6g6-3cm3-vf6c
MindsDB Eval Injection vulnerability
High Also affects mindsdb
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor