# CVE-2026-92207: MindsDB OpenBBtable Code Injection Remote Code Execution Vulnerability


- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-wc4f-6wjm-cqwf

## What is CVE-2026-92207?

CVE-2026-92207 is a high-severity vulnerability in MindsDB, published on 21 Oct 2026. 

### Official description

MindsDB OpenBBtable Code Injection Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of MindsDB. Authentication is required to exploit this vulnerability.

The specific flaw exists within the OpenBBtable class. The issue results from the lack of proper validation of a user-supplied string before using it to execute Python code. An attacker can leverage this vulnerability to execute code in the context of the service account. Was ZDI-CAN-28388.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-92207?


## How do I fix CVE-2026-92207?

No fix has been published for CVE-2026-92207 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92207 being exploited?

There is no known exploitation of CVE-2026-92207 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92207 and fix it if it is affected.

What it is: CVE-2026-92207 is a high-severity vulnerability in MindsDB, published on 21 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-92207 in the wild and no public exploit code.

Affected product: MindsDB. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92207/ (Markdown: https://insights.sbomify.com/CVE-2026-92207/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92207
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92207
- OSV: https://osv.dev/vulnerability/CVE-2026-92207

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92207/
Summaries are generated and may contain mistakes; the official description above is the record.