Quick answers
- Is CVE-2026-53557 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-53557 being exploited in the wild.
- How severe is CVE-2026-53557?
- Informational severity, with a CVSS score of 7.2, published 17 September 2026.
- Which products and versions are affected?
- DataEase SQLBot prior to 1.9.0.
- Is there a fix for CVE-2026-53557?
- A patch was published on 2026-09-06: Version 1.9.0 released with fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-53557 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-53557?
- 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 is a second-order SQL injection in the datasource management API. An authenticated user submits a crafted sheet["tableName"] value through POST /api/v1/datasource/ with an Excel datasource configuration; SQLBot stores this value without proper identifier escaping. When the datasource is deleted via DELETE /api/v1/datasource/{id}, the stored value is interpolated directly into cleanup SQL and executed by PostgreSQL. The attacker can exploit PostgreSQL's COPY TO PROGRAM command to execute arbitrary OS commands as the postgres process. Authentication is required to trigger the initial payload storage, but the exploitation occurs server-side during deletion. This issue was fixed in version 1.9.0 by implementing proper identifier sanitization.
Affected products
- DataEase SQLBot prior to 1.9.0
Timeline
- 2026-09-17: disclosed
- 2026-09-06: patched: Version 1.9.0 released with fix