UTC
High

mssql-mcp-core: SQL injection in mssql-mcp write tools via unparameterized table names and WHERE clauses

CVE-2026-63129 · GHSA-2m9m-6cr5-9x25 · published 2026-11-19

Severity
High
CVSS score
8.8
Chance of exploitation (EPSS)
0.55%
Fixed in
0.6.0
What it is

An actor who can supply tool arguments (a malicious or compromised MCP client, or an LLM agent steered via indirect prompt injection) could read, modify, or drop arbitrary data, bypass the read_data allow/deny validation and the preview/confirmation/maxRows safeguards, and conditionally achieve OS command execution.

What to do

Upgrade @connorbritain/mssql-mcp-core to 0.6.0 or later, and @connorbritain/mssql-mcp-reader to 0.5.0 or later, and @connorbritain/mssql-mcp-server to 0.6.0 or later, and @connorbritain/mssql-mcp-writer to 0.5.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Fixed in @connorbritain/mssql-mcp-core 0.6.0: All identifiers are validated against a strict allowlist and bracket-quoted via a shared helper. The free-form whereClause string parameter is removed (breaking change) and replaced with structured, parameterized filters ({ column, operator, value }) using an operator allowlist. Values are always bound, never interpolated. list_databases validates stateFilter against a fixed allowlist before use. Upgrade the consumer packages: mssql-mcp-reader 0.5.0, mssql-mcp-writer 0.5.0, mssql-mcp-server 0.6.0 (all depend on core ^0.6.0).

If you cannot upgrade yet

Upgrading is the only complete fix; the list_databases (stateFilter) sink is reachable even under READONLY=true and in the reader package. As defense in depth, run the server under a least-privilege SQL login with xp_cmdshell disabled, and restrict which MCP clients can invoke the tools.

Affected
PackageRegistryAffectedFixed in
@connorbritain/mssql-mcp-corenpm<= 0.5.00.6.0
@connorbritain/mssql-mcp-readernpm<= 0.4.20.5.0
@connorbritain/mssql-mcp-servernpm<= 0.5.20.6.0
@connorbritain/mssql-mcp-writernpm<= 0.4.20.5.0
Downstream in the Official MCP Registry

3 registered MCP servers install an affected version today, by the dependency versions a fresh install resolves.

  • io.github.ConnorBritain/mssql@connorbritain/mssql-mcp-core@0.1.5
  • io.github.ConnorBritain/mssql-reader@connorbritain/mssql-mcp-core@0.1.5
  • io.github.ConnorBritain/mssql-writer@connorbritain/mssql-mcp-core@0.1.5
See the trace →

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].