# CVE-2026-2531: MindsDB File Upload security.py clear_filename server-side request forgery

> Remote attackers can exploit a flaw in MindsDB's file upload handling to perform server-side request forgery, potentially accessing internal resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Feb 2026
- **Updated:** 23 Feb 2026
- **Also known as:** GHSA-6xw9-2p64-7622, PYSEC-2026-91

## What is CVE-2026-2531?

CVE-2026-2531 is a medium-severity server-side request forgery vulnerability in MindsDB, published on 16 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in MindsDB up to 25.14.1. This vulnerability affects the function clear_filename of the file mindsdb/utilities/security.py of the component File Upload. Such manipulation leads to server-side request forgery. The attack may be performed from remote. The exploit has been disclosed publicly and may be used. The name of the patch is 74d6f0fd4b630218519a700fbee1c05c7fd4b1ed. It is best practice to apply a patch to resolve this issue.

Weakness: CWE-918 (Server-Side Request Forgery)

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

3 open source packages ship an affected version, including mindsdb and MindsDB. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mindsdb` | PyPI | All versions to 25.14.1 | None |
| `mindsdb` | PyPI | All versions | 26.0.0rc1 |
| `MindsDB` | PyPI | All versions to 25.14.1 | None |

Products: Mindsdb Mindsdb.

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

Upgrade mindsdb to 26.0.0rc1 or later.

## Is CVE-2026-2531 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2531 exists.

## Other vulnerabilities in MindsDB

- [CVE-2024-24759](https://insights.sbomify.com/CVE-2024-24759/): MindsDB Vulnerable to Bypass of SSRF Protection with DNS Rebinding (critical 9.3)
- [CVE-2023-50731](https://insights.sbomify.com/CVE-2023-50731/): MindsDB has arbitrary file write in file.py (critical 9.1)
- [CVE-2023-38699](https://insights.sbomify.com/CVE-2023-38699/): MindsDB 'Call to requests with verify=False disabling SSL certificate checks, security issue.' issue (critical 9.1)
- [CVE-2024-45856](https://insights.sbomify.com/CVE-2024-45856/): MindsDB Cross-site Scripting vulnerability (critical 9.0)
- [CVE-2026-27483](https://insights.sbomify.com/CVE-2026-27483/): MindsDB has Path Traversal in /api/files Leading to Remote Code Execution (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-2531 is a medium-severity server-side request forgery vulnerability in MindsDB, published on 16 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-2531 exists.

Affected packages and fixed versions:
- mindsdb (PyPI): affected all versions up to 25.14.1; no fix listed
- mindsdb (PyPI): affected all versions; fixed in 26.0.0rc1
- MindsDB (PyPI): affected all versions up to 25.14.1; no fix listed

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-2531/ (Markdown: https://insights.sbomify.com/CVE-2026-2531/index.md)
```

## Sources

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

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