# CVE-2026-32950: SQLBot: RCE via SQL Injection in Excel Upload Endpoint

> Authenticated users can achieve remote code execution and database takeover via SQL injection in the Excel upload endpoint.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-7hww-8rj5-7rmm

## What is CVE-2026-32950?

CVE-2026-32950 is a high-severity SQL injection vulnerability in dataease SQLBot, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQLBot is an intelligent data query system based on a large language model and RAG. Versions prior to 1.7.0 contain a critical SQL Injection vulnerability in the /api/v1/datasource/uploadExcel endpoint that enables Remote Code Execution (RCE), allowing any authenticated user (even the lowest-privileged) to fully compromise the backend server. The root cause is twofold: Excel Sheet names are concatenated directly into PostgreSQL table names without sanitization (datasource.py#L351), and those table names are embedded into COPY SQL statements via f-strings instead of parameterized queries (datasource.py#L385-L388). An attacker can bypass the 31-character Sheet name limit using a two-stage technique—first uploading a normal file whose data rows contain shell commands, then uploading an XML-tampered file whose Sheet name injects a TO PROGRAM 'sh' clause into the SQL. Confirmed impacts include arbitrary command execution as the postgres user (uid=999), sensitive file exfiltration (e.g., /etc/passwd, /etc/shadow), and complete PostgreSQL database takeover. This issue has been fixed in version 1.7.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Fit2cloud Sqlbot.

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

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

## Is CVE-2026-32950 being exploited?

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

## Other vulnerabilities in dataease SQLBot

- [CVE-2026-33324](https://insights.sbomify.com/CVE-2026-33324/): SQLBot prompt injection allows arbitrary SQL execution and remote code execution (critical 9.4)
- [CVE-2026-32949](https://insights.sbomify.com/CVE-2026-32949/): SQLBot: SSRF to Arbitrary File Read (AFR) via Rogue MySQL (high 8.7)
- [CVE-2026-42463](https://insights.sbomify.com/CVE-2026-42463/): SQLBot: Unauthorized Access Vulnerability (high 8.6)
- [CVE-2026-32622](https://insights.sbomify.com/CVE-2026-32622/): SQLBot: Remote Code Execution via Terminology Poisoning (high 8.6)
- [CVE-2025-69285](https://insights.sbomify.com/CVE-2025-69285/): SQLBot uploadExcel Endpoint has Unauthenticated Arbitrary File Upload vulnerability (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32950 is a high-severity SQL injection vulnerability in dataease SQLBot, published on 20 Mar 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-32950 exists.

Affected product: dataease SQLBot. 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-32950/ (Markdown: https://insights.sbomify.com/CVE-2026-32950/index.md)
```

## Sources

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

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