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

CVE-2026-32622 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.6%.

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

SQLBot versions 1.5.0 and below contain a remote code execution vulnerability that allows authenticated users to execute arbitrary database commands by uploading malicious terminology files,…. A patch is available.

How to fix or mitigate CVE-2026-32622?

Within 24 hours: Identify all instances of SQLBot 1.5.0 and below in production and development environments. Within 7 days: Apply the vendor-released patch to upgrade all SQLBot instances to version 1.5.1 or later, and restrict upload API access to trusted administrators only during the patching window. Within 30 days: Conduct access review of all user accounts with terminology upload permissions, audit Excel upload logs for suspicious activity dating back 90 days, and implement API rate limiting on the Excel upload endpoint.

PostgreSQL CVE-2026-32622

EUVD-2026-13210 HIGH

Missing Authorization (CWE-862)

2026-03-19 GitHub_M

Authentication Bypass RCE PostgreSQL

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.6.0

EUVD ID Assigned

Mar 19, 2026 - 21:00 euvd

EUVD-2026-13210

Analysis Generated

Mar 19, 2026 - 21:00 vuln.today

CVE Published

Mar 19, 2026 - 20:55 nvd

HIGH 8.8

DescriptionGitHub Advisory

SQLBot is an intelligent data query system based on a large language model and RAG. Versions 1.5.0 and below contain a Stored Prompt Injection vulnerability that chains three flaws: a missing permission check on the Excel upload API allowing any authenticated user to upload malicious terminology, unsanitized storage of terminology descriptions containing dangerous payloads, and a lack of semantic fencing when injecting terminology into the LLM's system prompt. Together, these flaws allow an attacker to hijack the LLM's reasoning to generate malicious PostgreSQL commands (e.g., COPY ... TO PROGRAM), ultimately achieving Remote Code Execution on the database or application server with postgres user privileges. The issue is fixed in v1.6.0.

AnalysisAI

Remote code execution in SQLBot 1.5.0 and below allows authenticated users to inject malicious prompts through unsanitized terminology uploads, enabling attackers to manipulate the LLM into generating arbitrary PostgreSQL commands executed with database privileges. The vulnerability stems from missing permission checks on the Excel upload API combined with inadequate semantic isolation when injecting user-controlled data into the system prompt. An attacker can exploit this to achieve code execution on the database or application server running as the postgres user.

Technical ContextAI

Remote code execution allows an attacker to run arbitrary commands or code on the target system over a network without prior authentication. This vulnerability is classified as Missing Authorization (CWE-862).

RemediationAI

Apply vendor patches immediately. Restrict network access to vulnerable services. Implement network segmentation and monitoring for anomalous activity.