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.
CVE-2026-32950
This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(low)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 55%
- KEV
- Not listed
Published
March 20, 2026
Last Modified
June 17, 2026
Advisory Details (3)
Auto-updated Jul 27, 2026RCE via SQL Injection in Excel Upload Endpoint · Advisory · dataease/SQLBot · GitHub
Affected: v1.7.0.
https://github.com/dataease/SQLBot/security/advisories/GHSA-7hww-8rj5-7rmmv1.7.0
Patch available: dataease/SQLBot v1.7.0
https://github.com/dataease/SQLBot/releases/tag/v1.7.0commit 39f2203cec4b (dataease/SQLBot)
Patch available: dataease/SQLBot v1.7.0 (contains commit 39f2203cec4b)
https://github.com/dataease/SQLBot/commit/39f2203cec4bb4b0aa541710733fe7608e3d3c48Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:35 UTCEG score recompute
- 2026-07-27 14:27 UTCOSV refresh
Related CVEs(same CWE)
Same CWE
10 shownCWE-89 · CWE-78
Frequently asked(5)
What is CVE-2026-32950?
When was CVE-2026-32950 disclosed?
Is CVE-2026-32950 actively exploited?
What is the CVSS score of CVE-2026-32950?
How do I remediate CVE-2026-32950?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-32950
Is Your Infrastructure Affected by CVE-2026-32950?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.