SQLBot: RCE via SQL Injection in Excel Upload Endpoint
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-32950
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 5 Nov 2026, 02:05 UTC · Revision 1
Source evidence
SQLBot: RCE via SQL Injection in Excel Upload Endpoint
core-osv · Original sourcePublished 20 Mar 2026, 04:14 UTC
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.
osv:CVE-2026-32950
Complete source record
{
"id": "e74044e5589f6fd6cca95392916cf02691ce4636ba769929b19ed7ad61e675c3",
"url": "https://osv.dev/vulnerability/CVE-2026-32950",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "SQLBot: RCE via SQL Injection in Excel Upload Endpoint",
"summary": "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.",
"evidence": "osv:CVE-2026-32950",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-32950",
"aliases": [
"CVE-2026-32950",
"GHSA-7hww-8rj5-7rmm"
],
"metrics": [
{
"type": "CVSS_V4",
"score": "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"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/dataease/sqlbot",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "22e66c490fc67f77b94d71dfdb048270e9b6641a"
},
{
"fixed": "39f2203cec4bb4b0aa541710733fe7608e3d3c48"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:fit2cloud:sqlbot:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "1.7.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "39f2203cec4bb4b0aa541710733fe7608e3d3c48"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "22e66c490fc67f77b94d71dfdb048270e9b6641a"
}
],
"source": "REFERENCES_TAG",
"original_tag": "v1.7.0"
}
]
}
}
],
"versions": [
"v1.6.0",
"v1.5.0",
"v1.4.0",
"v1.3.0",
"v1.2.1",
"v1.2.0",
"v1.1.4",
"v1.1.3",
"v1.1.2",
"v1.1.0",
"v1.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-32950.json"
}
}
],
"modified": "2026-10-28T02:30:42.063975738Z",
"provider": "osv",
"references": [
"https://github.com/dataease/SQLBot/releases/tag/v1.7.0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/32xxx/CVE-2026-32950.json",
"https://github.com/dataease/SQLBot/security/advisories/GHSA-7hww-8rj5-7rmm",
"https://nvd.nist.gov/vuln/detail/CVE-2026-32950",
"https://github.com/dataease/SQLBot/commit/39f2203cec4bb4b0aa541710733fe7608e3d3c48"
],
"provider_metadata": {
"cwe_ids": [
"CWE-78",
"CWE-89"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/32xxx/CVE-2026-32950.json"
}
},
"related_cves": [
{
"value": "CVE-2026-32950",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 509347,
"published_at": "2026-03-20T04:14:45.64+00:00"
}