CVE-2026-130595
Deferred Deferred - Pending Action

SQL Injection Risk in SQLBot Due to PostgreSQL Denylist Bypass

Vulnerability report for CVE-2026-130595, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-17

Last updated on: 2026-11-17

Assigner: VulnCheck

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-17
Last Modified
2026-11-17
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
dataease SQLBot From 1.10.0 (inc) to 1.10.3 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-184 The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

SQLBot versions 1.10.0 through 1.10.3 have a flaw where the denylist for dangerous PostgreSQL functions is not applied correctly. The system checks for functions using 'postgresql' but the actual lookups use 'pg'. This allows authenticated users to bypass restrictions and use functions like pg_read_file, pg_write_file, lo_import, or lo_export to read or write files on the database host.

Detection Guidance

Check for unauthorized file access or modifications in PostgreSQL logs. Look for queries using pg_read_file, pg_write_file, lo_import, or lo_export functions. Review SQLBot logs for denylist bypass attempts.

Impact Analysis

An attacker with authenticated access could exploit this to read sensitive files on the database server or write malicious files, potentially leading to further compromise of the system or data theft.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection principles or HIPAA's requirements for safeguarding protected health information. Organizations using SQLBot may face compliance violations and potential penalties.

Mitigation Strategies

Upgrade SQLBot to a version that fixes the denylist issue. Restrict PostgreSQL function permissions to prevent unauthorized file operations. Monitor for suspicious queries or file access patterns.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-130595. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...