# CVE-2026-130595: SQLBot 1.10.0 through 1.10.3 PostgreSQL Dangerous-Function Denylist Bypass via Key Mismatch


- **Severity:** Medium 6.0 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-f9wg-44c5-frh4

## What is CVE-2026-130595?

CVE-2026-130595 is a medium-severity vulnerability in dataease SQLBot, published on 17 Nov 2026. 

### Official description

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.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

## Which versions are affected by CVE-2026-130595?

1 open source package ship an affected version, including dataease/sqlbot.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `dataease/sqlbot` | GitHub | `pkg:github/dataease/sqlbot` | From 1.10.0 to 1.10.3 | None |

## How do I fix CVE-2026-130595?

No fix has been published for CVE-2026-130595 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-130595 being exploited?

There is no known exploitation of CVE-2026-130595 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130595 and fix it if it is affected.

What it is: CVE-2026-130595 is a medium-severity vulnerability in dataease SQLBot, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130595 in the wild and no public exploit code.

Affected packages and fixed versions:
- dataease/sqlbot (GitHub): affected from 1.10.0 up to 1.10.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130595/ (Markdown: https://insights.sbomify.com/CVE-2026-130595/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130595
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130595
- OSV: https://osv.dev/vulnerability/CVE-2026-130595

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130595/
Summaries are generated and may contain mistakes; the official description above is the record.
