CVE-2026-53554: SQLBot: Arbitrary File Write via parseExcel Leading to Code Execution Through Alembic Import Processing

Published Sep 17, 2026
·
Updated

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

1 affected component
SQLBot<1.9.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade SQLBot to a version that resolves this vulnerability.

    Fixed in 1.9.0

Event History

Sep 17, 2026
CVE Published
via MITRE·09:38 PM
Data Sourced
via MITRE·09:38 PM
DescriptionWeakness

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203