# CVE-2026-86123: SQL Chat Unauthenticated Database-Connection Proxy in the /api/connection Endpoints

> Unauthenticated attackers can use SQL Chat API endpoints to connect to internal databases and execute arbitrary SQL queries, enabling data theft and network pivoting.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-7xvg-gx2w-r5cc

## What is CVE-2026-86123?

CVE-2026-86123 is a critical server-side request forgery vulnerability in sqlchat, published on 5 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL Chat contains four unauthenticated API endpoints that accept client-supplied database connection parameters and execute arbitrary SQL queries against attacker-specified hosts. Attackers can connect to internal databases, execute SQL commands, enumerate schemas, and pivot into the server's network without authentication.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-86123 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86123 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86123 is a critical server-side request forgery vulnerability in sqlchat, published on 5 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86123 exists.

Affected product: sqlchat. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-86123/ (Markdown: https://insights.sbomify.com/CVE-2026-86123/index.md)
```

## Sources

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

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