# CVE-2026-32622: SQLBot: Remote Code Execution via Terminology Poisoning

> Attackers can achieve remote code execution by uploading malicious terminology that hijacks the LLM to generate dangerous database commands.

- **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:** 19 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-m7q7-vhw9-q7m3

## What is CVE-2026-32622?

CVE-2026-32622 is a high-severity code injection vulnerability in dataease SQLBot, published on 19 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 1.5.0 and below contain a Stored Prompt Injection vulnerability that chains three flaws: a missing permission check on the Excel upload API allowing any authenticated user to upload malicious terminology, unsanitized storage of terminology descriptions containing dangerous payloads, and a lack of semantic fencing when injecting terminology into the LLM's system prompt. Together, these flaws allow an attacker to hijack the LLM's reasoning to generate malicious PostgreSQL commands (e.g., COPY ... TO PROGRAM), ultimately achieving Remote Code Execution on the database or application server with postgres user privileges. The issue is fixed in v1.6.0.

Weakness: CWE-862 (Missing Authorization), CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Fit2cloud Sqlbot.

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

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

## Is CVE-2026-32622 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32622 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-32950](https://insights.sbomify.com/CVE-2026-32950/): SQLBot: RCE via SQL Injection in Excel Upload Endpoint (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-32622 and fix it if it is affected.

What it is: CVE-2026-32622 is a high-severity code injection vulnerability in dataease SQLBot, published on 19 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-32622 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-32622/ (Markdown: https://insights.sbomify.com/CVE-2026-32622/index.md)
```

## Sources

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

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