Quick answers
- Is CVE-2026-53554 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53554 being exploited in the wild.
- How severe is CVE-2026-53554?
- Informational severity, with a CVSS score of 8.8, published 17 September 2026.
- Which products and versions are affected?
- DataEase SQLBot prior to 1.9.0.
- Is there a fix for CVE-2026-53554?
- A patch was published on 2026-09-17: Fixed in version 1.9.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53554 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-53554?
- Check whether you run DataEase SQLBot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the POST /api/v1/datasource/parseExcel endpoint, which accepts multipart file uploads without proper validation of the filename. An attacker can craft a multipart upload with a double-extension filename (e.g., "malicious.py.xlsx") that exploits path traversal and filename handling to write attacker-controlled Python code to /opt/sqlbot/app/alembic/versions/. The endpoint writes file content to disk before spreadsheet parsing and validation complete, meaning malicious files persist even if validation fails. When SQLBot starts or runs migrations, Alembic automatically imports and executes module-level code from files in the versions directory, achieving arbitrary code execution. The fix in version 1.9.0 sanitizes filenames to strip path components and prevents double-extension attacks.
Affected products
- DataEase SQLBot prior to 1.9.0
Timeline
- 2026-09-17: disclosed
- 2026-09-17: patched: Fixed in version 1.9.0