CVE-2026-130595

SQLBot 1.10.0 through 1.10.3 PostgreSQL Dangerous-Function Denylist Bypass via Key Mismatch

Published Nov 17, 2026 CVSS 4.0 · 6 Medium EPSS n/a KEV · Not listed
Description
SQLBot 1.10.0 through 1.10.3 fails to apply its PostgreSQL dangerous-function denylist because DS_SPECIFIC_DANGEROUS_FUNCTIONS uses 'postgresql' while lookups use the 'pg' type. Authenticated users can steer LLM-generated SQL past check_sql_read() using pg_read_file, pg_write_file, lo_import or lo_export to read or write files on the database host.

Analysis

AI-generated

Technical impact

SQLBot 1.10.0 through 1.10.3 contains a logic flaw that allows a key mismatch in the PostgreSQL dangerous‑function denylist. The DS_SPECIFIC_DANGEROUS_FUNCTIONS dictionary uses the key ‘postgresql’ while the lookup routine expects the key ‘pg’, causing the functions pg_read_file, pg_write_file, lo_import, and lo_export to bypass the check_sql_read() check. Authenticated users can incorporate these functions into LLM‑generated SQL, enabling the reading or writing of arbitrary files on the database host. This is a type of input validation error described by CWE‑184.

Affected Systems

All deployments of DataEase SQLBot version 1.10.0, 1.10.1, 1.10.2, and 1.10.3, wherever the impacted code paths in db.py are active. The issue is independent of the hosting environment and will affect any installation that generates SQL through the LLM component.

Risk and Exploitability

The CVSS score of 6.0 indicates a moderate severity. The EPSS score is not available, so the precise likelihood of exploitation cannot be quantified, but the flaw can be triggered by any authenticated user with access to the LLM‑generated SQL path. The vulnerability is not listed in the CISA KEV catalog. Attackers with legitimate credentials can read or write files on the database host, representing a local privilege escalation that could exfiltrate sensitive data or alter system files.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to SQLBot 1.10.4 or newer, which aligns the denylist key with the lookup key and removes the bypass.
  • If an upgrade is not immediately feasible, apply the upstream hotfix commit 67d213fc3920c29e8ca7c27c5ea2334bdebe284d to correct the key mismatch.
  • Reconfigure the database user that runs SQLBot so that it does not have the permissions for pg_read_file, pg_write_file, lo_import, or lo_export, thereby limiting the impact of the bypass.

Generated by OpenCVE AI on November 17, 2026 at 16:27 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Dataease
Dataease sqlbot
Vendors & Products Dataease
Dataease sqlbot
Type Values Removed Values Added
Description SQLBot 1.10.0 through 1.10.3 fails to apply its PostgreSQL dangerous-function denylist because DS_SPECIFIC_DANGEROUS_FUNCTIONS uses 'postgresql' while lookups use the 'pg' type. Authenticated users can steer LLM-generated SQL past check_sql_read() using pg_read_file, pg_write_file, lo_import or lo_export to read or write files on the database host.
Title SQLBot 1.10.0 through 1.10.3 PostgreSQL Dangerous-Function Denylist Bypass via Key Mismatch
Weaknesses CWE-184
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N'}

cvssV4_0

{'score': 6, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-184

    Incomplete List of Disallowed Inputs

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 17, 2026, 4:16 PM
Reserved
Nov 17, 2026, 12:32 PM
Status
Deferred
Published
Nov 17, 2026, 2:17 PM
Modified
Nov 17, 2026, 5:18 PM