CVE-2026-86123

SQL Chat exposes four unauthenticated API endpoints that accept client-supplied database connection parameters and forward the caller's SQL statements to whichever database host those parameters specify. An unauthenticated remote attacker can abuse this by supplying their own host and connection details, causing the SQL Chat server to connect to attacker-specified databases, including internal ones, and execute arbitrary SQL, enumerate schemas, and reach other services on the server's network (server-side request forgery, CWE-918). The critical CVSS 4.0 score of 9.4 with high attack complexity reflects that impact depends on which internal networks and databases the SQL Chat server is able to reach. Any organization running SQL Chat is affected, with the greatest risk where the application is internet-exposed or sits on a network with access to sensitive internal databases. No public proof-of-concept, KEV listing, or known in-the-wild exploitation exists, and EPSS estimates only a 0.3% chance of exploitation within 30 days.

What to do: Until a patched release is identified (none is specified in the current data), restrict access to the SQL Chat API endpoints, for example behind an authenticating reverse proxy, and firewall the SQL Chat server's outbound network access so it can only connect to approved database hosts. Check whether your instance is internet-exposed and review internal database and network logs for unexpected connections or queries originating from the SQL Chat server. Monitor the vendor advisory for a fixed version and apply it when available.