Skip to main content
VulnerabilityPublished Updated

CVE-2026-32950: dataease SQLBot · SQL Injection

Affects dataease SQLBotSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.6 High : upgrade to 1.7.0 soon.

Data as of 1 Nov 2026, 22:58 UTC

CVSS 4.0 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.7.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 1 Nov 2026.

What to do

Upgrade SQLBot and dataease/SQLBot to 1.7.0.

Affected software

ProductAffectedFixed in
dataeaseSQLBotAffected
  • <1.7.0
Fixed in
  • 1.7.0
GitHubdataease/SQLBotpkg:github/dataease/SQLBotOther threatsAffected
  • <1.7.0
Fixed in
  • 1.7.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should immediately upgrade SQLBot to version 1.7.0 or later where the issue is fixed. Until upgrade is possible, restrict access to the /api/v1/datasource/uploadExcel endpoint to trusted users only and enforce strong authentication and authorization controls to limit who can upload Excel files. Implement network segmentation and monitoring to detect unusual database or shell command activity. Review and sanitize all user-supplied inputs, especially Excel sheet names, ensuring they are validated against a strict whitelist of allowed characters and lengths before use in SQL statements. Avoid using string concatenation or f-strings for SQL commands; instead, use parameterized queries or prepared statements. Employ database roles with least privilege, ensuring the postgres user or equivalent does not have unnecessary OS-level permissions. Conduct regular audits of database logs and system activity to detect potential exploitation attempts. Finally, educate developers on secure coding practices to prevent similar injection flaws.

Description

SQLBot is an intelligent data query system based on a large language model and RAG. Versions prior to 1.7.0 contain a critical SQL Injection vulnerability in the /api/v1/datasource/uploadExcel endpoint that enables Remote Code Execution (RCE), allowing any authenticated user (even the lowest-privileged) to fully compromise the backend server. The root cause is twofold: Excel Sheet names are concatenated directly into PostgreSQL table names without sanitization (datasource.py#L351), and those table names are embedded into COPY SQL statements via f-strings instead of parameterized queries (datasource.py#L385-L388). An attacker can bypass the 31-character Sheet name limit using a two-stage technique—first uploading a normal file whose data rows contain shell commands, then uploading an XML-tampered file whose Sheet name injects a TO PROGRAM 'sh' clause into the SQL. Confirmed impacts include arbitrary command execution as the postgres user (uid=999), sensitive file exfiltration (e.g., /etc/passwd, /etc/shadow), and complete PostgreSQL database takeover. This issue has been fixed in version 1.7.0.

References

Community reviews

Loading reviews…