What is the CVSS score of CVE-2026-32950?

CVE-2026-32950 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of PostgreSQL are affected by CVE-2026-32950?

SQLBot versions before 1.7.0 contain a SQL injection vulnerability in the Excel upload endpoint that allows authenticated users to execute arbitrary commands on the backend database server and…. A patch is available.

How to fix or mitigate CVE-2026-32950?

Within 24 hours: Inventory all SQLBot deployments and document current versions; restrict network access to the /api/v1/datasource/uploadExcel endpoint to trusted administrators only. Within 7 days: upgrade all SQLBot instances to version 1.7.0 or later per vendor advisory. Within 30 days: conduct access logs review for the uploadExcel endpoint from the past 90 days to identify any suspicious activity; perform database integrity audit to detect unauthorized modifications.

PostgreSQL CVE-2026-32950

EUVD-2026-13543 HIGH

OS Command Injection (CWE-78)

2026-03-20 security-advisories@github.com

SQLi RCE PostgreSQL Command Injection

8.8

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 06:20 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

1.7.0

EUVD ID Assigned

Mar 20, 2026 - 08:37 euvd

EUVD-2026-13543

Analysis Generated

Mar 20, 2026 - 08:37 vuln.today

CVE Published

Mar 20, 2026 - 05:16 nvd

HIGH 8.8

DescriptionGitHub Advisory

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.

AnalysisAI

SQLBot, an intelligent data query system based on large language models and RAG, contains a critical SQL injection vulnerability in the /api/v1/datasource/uploadExcel endpoint that allows authenticated users with minimal privileges to achieve remote code execution on the backend server. SQLBot versions prior to 1.7.0 are affected, and attackers can exploit unsafe concatenation of Excel sheet names into PostgreSQL table names and COPY statements to inject malicious SQL commands. The vulnerability enables arbitrary command execution as the postgres user, database takeover, and sensitive file exfiltration including /etc/passwd and /etc/shadow.

Technical ContextAI

This vulnerability affects SQLBot, a Python-based data query system that integrates large language models with Retrieval-Augmented Generation (RAG) for natural language database queries. The root cause maps to CWE-78 (OS Command Injection), stemming from two critical flaws in datasource.py: Excel sheet names are directly concatenated into PostgreSQL table names without sanitization at line 351, and these unsanitized table names are embedded into COPY SQL statements using Python f-strings rather than parameterized queries at lines 385-388. Attackers exploit PostgreSQL's COPY TO PROGRAM feature, which allows SQL statements to invoke shell commands, by uploading specially crafted Excel files with XML-tampered sheet names that inject a TO PROGRAM 'sh' clause. The two-stage attack bypasses the 31-character sheet name limit by first uploading normal data containing shell commands, then uploading a file whose sheet name completes the SQL injection payload.

RemediationAI

Upgrade SQLBot to version 1.7.0 or later immediately, as documented in the release notes at https://github.com/dataease/SQLBot/releases/tag/v1.7.0. The fix implemented in commit 39f2203cec4bb4b0aa541710733fe7608e3d3c48 addresses the unsafe string concatenation by implementing proper input sanitization for Excel sheet names and replacing f-string SQL construction with parameterized queries. Until patching is completed, implement compensating controls including restricting access to the /api/v1/datasource/uploadExcel endpoint to only highly trusted administrators, implementing strict input validation on file uploads at the web application firewall or reverse proxy layer, and monitoring PostgreSQL logs for suspicious COPY TO PROGRAM statements. Organizations should audit existing uploaded Excel files for potential malicious sheet names and review postgres user command execution logs for signs of prior exploitation.