CVE-2026-130595
SQLBot 1.10.0 through 1.10.3 fails to apply its PostgreSQL …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/dataease/SQLBot/blob/96f06c7eade60ecf3e6af0313821373761d1fb85/backend/apps/db/d
- github.com/dataease/SQLBot/commit/67d213fc3920c29e8ca7c27c5ea2334bdebe284d
- github.com/dataease/SQLBot/issues/1438
- www.vulncheck.com/advisories/sqlbot-1.10.0-through-1.10.3-postgresql-dangerous-function-de
- nvd.nist.gov/vuln/detail/CVE-2026-130595
- cve.org/CVERecord?id=CVE-2026-130595
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.