Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-86123 – Unauthenticated SQL Execution / SSRF – SQL Chat (sqlchat/sqlchat, commit ≤ 665af87

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-86123 is a critical vulnerability in SQL Chat, an open-source chat-based SQL client and editor, in which the /api/connection/* API endpoints accept client-supplied database connection parameters (host, port, credentials, engine type) and use them to open connections and execute SQL statements without requiring any authentication. This allows a remote, unauthenticated attacker to force the SQL Chat server to connect to and execute arbitrary SQL queries against attacker-specified database hosts, effectively turning the application into an SSRF and database-access proxy. The issue carries a CVSS v3.1 base score of 8.7 (High) / CVSS v4.0 score of 9.4 (Critical).

Technical details

  • Root cause: The API route handlers under /api/connection/ (including execute, test, db_schema, and db) build a database connector directly from connection parameters supplied in the request body, with no session, token, or identity verification performed before the connector is instantiated and used.
  • Trigger conditions: An attacker sends a crafted POST request to one of the affected endpoints (e.g., /api/connection/execute) containing a connection object (host, port, engine type, credentials) plus a db name and SQL statement; the server executes the request server-side and returns query results or error details to the requester.
  • Attack vector: Network — no authentication or user interaction is required. Because the connection target is entirely attacker-controlled, the endpoints can also be abused to probe or reach internal-only hosts and services reachable from the SQL Chat server (SSRF), in addition to any externally reachable database the attacker already knows credentials for.
  • Impact: Unauthorized execution of arbitrary SQL statements against attacker-specified or internal databases, enumeration of internal network/database infrastructure, and potential exfiltration of data from systems the SQL Chat server can reach. The vulnerability is scored with high confidentiality and integrity impact.

Affected software

  • Product: SQL Chat (sqlchat/sqlchat, self-hosted deployments)
  • Affected versions: All versions/commits up to and including git commit 665af875413affadfeefff81794f1d7758782bc2
  • Vulnerable endpoints: POST /api/connection/execute, POST /api/connection/test, POST /api/connection/db_schema, POST /api/connection/db

Severity

  • CVSS v3.1 Base Score: 8.7 (High) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N
  • CVSS v4.0 Base Score: 9.4 (Critical) — 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

Mitigation and recommended actions

  • Immediate: As of this writing, no fixed release or patched commit addressing this issue has been published by the SQL Chat maintainers; the referenced GitHub issue remains open with no confirmed remediation commit. Security teams should monitor the sqlchat/sqlchat repository for a fix and upgrade to a patched version as soon as one is released.
  • If no patch is available:
    • Do not expose self-hosted SQL Chat instances directly to the internet; place them behind authentication (e.g., a reverse proxy with SSO/basic auth) that gates access to all /api/connection/* routes.
    • Restrict outbound network access from the host running SQL Chat so it cannot reach internal/private address ranges (RFC1918, loopback, link-local) that should not be queryable by the application.
    • Apply network-level allowlisting so the application can only connect to explicitly approved database hosts.
    • Monitor logs for unexpected connection attempts to unfamiliar hosts or ports originating from the SQL Chat deployment.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge