CVE-2026-53554: SQLBot: Arbitrary File Write via parseExcel Leading to Code Execution Through Alembic Import Processing
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
SQLBotto a version that resolves this vulnerability.Fixed in 1.9.0
Event History
Frequently Asked Questions
Which deployments are affected?
SQLBot versions prior to 1.9.0 are affected if an attacker can submit a crafted multipart upload to the POST /api/v1/datasource/parseExcel endpoint.
Does a failed spreadsheet upload prevent exploitation?
No. The uploaded content is written before spreadsheet parsing and validation complete, so a parsing failure can return an error while leaving the attacker-controlled file on disk.
What must happen for the planted file to execute?
After a crafted upload places a Python source file in /opt/sqlbot/app/alembic/versions/, a subsequent SQLBot startup or migration-processing event causes Alembic to import it and execute its module-level statements in the SQLBot runtime.
What can be done if upgrading is not immediately possible?
Restrict access to the parseExcel upload endpoint so untrusted users cannot submit multipart uploads, and inspect /opt/sqlbot/app/alembic/versions/ for unexpected Python files. Remove any suspected planted files before restarting SQLBot or running migration processing.