CVE-2026-130595
SQLBot’s PostgreSQL safety check could miss restricted database functions
dataease · SQLBot
First documented disclosure · Review checkpoint
Summary
A dialect-name mismatch could let generated SQL bypass a database-function safety check.
Severity and exploitation evidence
Medium · 6.0/10 · CVSS 4.0. Severity source.
Exploitation not established: Malicious exploitation status remains unverified in the reviewed sources.
Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.
How the weakness works
The PostgreSQL denylist and the lookup used different identifiers.
Conditions required
An authenticated user can influence generated SQL and the database role can perform the affected file operations.
Potential impact
Generated SQL can read or write files accessible to the database host account.
Affected versions and configurations
1.10.0 through 1.10.3.
Fix and mitigation status
Correction commit 67d213fc3920c29e8ca7c27c5ea2334bdebe284d. A packaged fixed release remains unverified.
Practical next steps
Apply the reviewed correction or deploy a release verified to contain it. Restrict the database role’s file privileges.
Operating lesson
Use database permissions to enforce the safety boundary of generated SQL.
Evidence and limits
Original disclosure 2026-11-03. The CVE Program published this record 2026-11-17. The maintainer correction is dated November 5. The reviewed release listing still ends at 1.10.3.
Sources
- VulnCheck CVE authority record
Primary source ·
- SQLBot original advisory
Primary source ·
- ENISA EUVD-2026-127009
Primary source ·