Skip to main content
CVE-2026-130595VulnerabilityPublished

SQLBot 1.10.0 through 1.10.3 fails to apply its PostgreSQL dangerous-function denylist because

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-130595· Medium 6.0

Not known to be exploited · CVSS 6.0 Medium.

Data as of 17 Nov 2026, 16:52 UTC

CVSS 4.0 base score
6.0Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.06.0
CNA (VulnCheck)CVSS 3.15.9
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
dataeaseSQLBotAffected
  • >=1.10.0 <=1.10.3
Fixed in–
GitHubSQLBotpkg:github/SQLBotOther threatsAffected
  • >=1.10.0 <=1.10.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, restrict authenticated user privileges to prevent execution of dangerous PostgreSQL functions and monitor for unusual database activity involving file operations.

Description

SQLBot versions 1.10.0 through 1.10.3 contain a vulnerability where the PostgreSQL dangerous-function denylist is not properly applied due to a mismatch in identifier strings. This allows authenticated users to bypass the check_sql_read() function and execute dangerous PostgreSQL functions such as pg_read_file, pg_write_file, lo_import, and lo_export, potentially enabling reading or writing files on the database host.

References

Community reviews

Loading reviews…