CVE-2026-130595
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 …
Impact
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.
An attacker can exploit this over the network, with a regular user account, without any action by a user. Specific conditions have to be met, which makes an attack harder. If it succeeds: high risk of data being read, low risk of data or systems being changed.
Affected products · Dataease
| Product | Affected versions |
|---|---|
| SQLBot | from 1.10.0 through 1.10.3 Version 1.10.0 ≤1.10.3 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/dataease/SQLBot/issues/1438
- https://github.com/dataease/SQLBot/commit/67d213fc3920c29e8ca7c27c5ea2334bdebe284d
- https://github.com/dataease/SQLBot/blob/96f06c7eade60ecf3e6af0313821373761d1fb85/backend/apps/db/db.py#L1155-L1182
- https://www.vulncheck.com/advisories/sqlbot-1.10.0-through-1.10.3-postgresql-dangerous-function-denylist-bypass-via-key-mismatch
- https://github.com/advisories/GHSA-f9wg-44c5-frh4
- https://nvd.nist.gov/vuln/detail/CVE-2026-130595