High severity · published Sep 17, 2026
CVE-2026-53554
SQLBot: Arbitrary File Write via parseExcel Leading to Code Execution Through Alembic Import Processing
7.3
CVSS
0.4%
EPSS
No
On KEV
Description
SQLBot is an intelligent Text-to-SQL system based on large language models and RAG. Prior to 1.9.0, the POST /api/v1/datasource/parseExcel endpoint in backend/apps/datasource/api/datasource.py uses attacker-controlled multipart filename data when selecting where uploaded content is stored, writes the content before spreadsheet parsing and validation finish, and can transform a double-extension filename into a Python source file. An attacker able to submit a crafted multipart upload can use these behaviors to place attacker-controlled content in /opt/sqlbot/app/alembic/versions/ even when a spreadsheet parsing failure after the file write causes the endpoint to return an error. The planted file remains on disk, and subsequent SQLBot startup or migration processing causes Alembic to import the module and execute its module-level statements in the SQLBot application runtime. This issue is fixed in version 1.9.0.
Exploitation
Is it being used?
Exploit prediction (EPSS)0.4% · higher than 36% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
SQ
SQLBot · dataease
< 1.9.0 · source: vendor
Affected product
SQ
SQLBot
dataease
More from SQLBot
8.8
CVE-2026-33324
SQLBot prompt injection allows arbitrary SQL execution and remote code execution
8.8
CVE-2026-32950
SQLBot: RCE via SQL Injection in Excel Upload Endpoint
8.8
CVE-2026-32622
SQLBot: Remote Code Execution via Terminology Poisoning
8.1
CVE-2026-42463
SQLBot: Unauthorized Access Vulnerability
7.7
CVE-2026-53557
SQLBot: Second-Order SQL Injection via Excel Datasource Leading to Remote Command Execution