# CVE-2026-53557: SQLBot: Second-Order SQL Injection via Excel Datasource Leading to Remote Command Execution

> An authenticated user can achieve remote code execution via second-order SQL injection in the Excel datasource configuration of SQLBot.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 17 Sep 2026
- **Updated:** 22 Sep 2026
- **Also known as:** GHSA-vxwj-843f-9c9g

## What is CVE-2026-53557?

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

### Official description

SQLBot is an intelligent Text-to-SQL system based on large language models and RAG. Prior to 1.9.0, an authenticated user can supply a crafted sheet["tableName"] value in the Excel datasource configuration submitted through POST /api/v1/datasource/, and SQLBot stores that value without safe identifier handling. When the same datasource is later removed through DELETE /api/v1/datasource/{id}, the stored value is interpolated into datasource cleanup SQL and executed by PostgreSQL. This second-order SQL injection can invoke PostgreSQL COPY TO PROGRAM and execute arbitrary operating-system commands with the privileges of the postgres process inside the SQLBot container. This issue is fixed in version 1.9.0.

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

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


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

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

## Is CVE-2026-53557 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-53557 is a high-severity SQL injection vulnerability in dataease SQLBot, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-53557 in the wild and no public exploit code.

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

## Sources

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

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