AI Stack Alert High CVE-2026-130595 For AppSec, AI Eng, SOC / IR AI-assisted
CVE-2026-130595: SQLBot 1.10.0-1.10.3 PostgreSQL dangerous-function denylist not applied
SQLBot versions 1.10.0 through 1.10.3 fail to apply their PostgreSQL dangerous-function denylist. The denylist uses the type name 'postgresql' while lookups use 'pg', so the check is skipped. Authenticated users can steer LLM-generated SQL past check_sql_read() to read or write files on the database host.
Why it matters
Any authenticated SQLBot user can reach server-side file read and write through PostgreSQL functions, exposing files on the database host. The CVSS base score is 6.
Do this
- Identify SQLBot deployments running versions 1.10.0 through 1.10.3 and upgrade to a fixed release once available from the vendor.
- Restrict SQLBot user accounts to least privilege and review which users can submit natural-language queries.
- Run the SQLBot PostgreSQL service account with minimal filesystem access and revoke privileges on pg_read_file, pg_write_file, lo_import and lo_export where not needed.
- Review PostgreSQL logs for calls to pg_read_file, pg_write_file, lo_import or lo_export originating from SQLBot connections.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 6CVSS
- NoPublic PoC
- 34/100Priority
- 70%Confidence
Evidence
“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.”
Sources
Affected / related
SQLBot, SQLBot 1.10.0-1.10.3, LLM-generated SQL denylist bypass
Published 2026-11-17 14:17 UTC · updated 2026-11-17 16:35 UTC · AI-assisted summary, checked against quoted sources · How we score