External risk intelligence

SQL Chat Unauthenticated Database Connection Proxy Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-86123

The vulnerability exists in API endpoints of a web application designed to facilitate database interactions. As a web application, these API endpoints are typically exposed to the internet or reachable from external clients to function as intended, placing them in a position where they are commonly accessible in real-world deployments.

Server-Side Request Forgery

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability impacts SQL Chat's API endpoints, allowing unauthenticated access to connect to and execute arbitrary SQL queries against internal databases. The primary concern is to confirm if this technology is in use and assess potential exposure.

Allows unauthenticated database access.
Impacts systems processing sensitive data.
Confirm usage and assess exposure risk.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted requests to unauthenticated API endpoints. These endpoints accept user-provided database connection details, allowing the attacker to execute arbitrary SQL queries on external or internal databases. This could grant unauthorized access to sensitive data, enable schema enumeration, and potentially provide a pivot point for further network compromise.

Unauthenticated API endpoints accessible externally.
Sending malicious database connection parameters.
Unauthorized SQL query execution and network pivot.

Live Threat

Current exploitation, exposure, and threat context

SQL Chat's unauthenticated API endpoints could allow an attacker to connect to internal databases, execute arbitrary SQL queries, and explore network configurations when supported by the advisory. This could expose sensitive system and user data, or allow unauthorized actions within the connected network.

System and user data.
Unauthenticated API endpoint access.
Unauthorized database access and control.

Operational Fix

Recommended remediation, mitigation, and detection steps

The core vulnerability lies within SQL Chat's unauthenticated API endpoints, which could be managed by application owners or platform teams. Initial actions should focus on inventorying all SQL Chat instances, determining their reachability and criticality, identifying the accountable teams, and then developing a phased remediation plan based on risk.

Application owners must prioritize this issue.
Verify SQL Chat instance reachability and business impact.
Plan remediation based on identified asset ownership.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is SQL Chat?

SQL Chat is an open-source web application designed to help users interact with databases using natural language. It functions as a chat interface that generates and runs SQL queries, acting as an intermediary between the user and their database management systems. Because it is a web-based tool, it is often deployed to allow teams to query data without needing to write complex code directly.

What does CWE-918 mean in the context of CVE-2026-86123?

This CVE involves Server-Side Request Forgery, classified as CWE-918. In plain terms, the application acts as a proxy that can be tricked into making requests to targets it was not intended to reach. Because the API endpoints do not verify the user's identity, an attacker can supply their own database connection details, forcing the server to send unauthorized SQL commands to internal or external systems on their behalf.

How is this vulnerability triggered?

An attacker triggers the vulnerability by sending specially crafted web requests to specific, unprotected API endpoints within the application. These requests provide the server with external database parameters. The bug is not triggered by standard usage or legitimate chat sessions; it requires an actor to purposefully provide malicious connection data to the application's backend API, bypassing the intended authentication flow entirely.

Is my instance at risk according to Halo Surface Signal?

Halo Surface Signal indicates a 'Likely' risk level for this issue. Since the vulnerability resides in API endpoints designed for database interactions, these components are frequently exposed to the internet to remain functional. Because they are web-facing by nature, they are often reachable by external parties, making it critical to verify if your specific instance is accessible outside of your internal network.

What should I do if I run SQL Chat?

Your first step is to inventory all instances of SQL Chat across your environment to understand where it is deployed. Determine which of these instances are reachable from the internet versus those on private networks. Once identified, work with the teams responsible for these systems to assess their business impact and restrict access to the API endpoints while you plan and implement the necessary updates or security controls.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.