Skip to main content
Menu
CVEs

CVE

ConnorBritain SQL injection in write tools via table names and filters

Affects mssql-mcp-core and mssql-mcp-server before 0.6.0, and mssql-mcp-reader and mssql-mcp-writer before 0.5.0, where table names and WHERE clauses are interpolated into SQL. Fixed in 0.6.0 and 0.5.0.

CVE-2026-63129Published Updated Summary written by a model

8.8HighCNA
Exploited
No known exploitation
Fix
Fixed in mssql-mcp-core 0.6.0 · mssql-mcp-reader 0.5.0 · mssql-mcp-writer 0.5.0 · mssql-mcp-server 0.6.0
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Uses the update_data, delete_data, insert_data, execute_transaction, create_table, create_index or drop_table tools, which interpolate tableName and whereClause into SQL Uses the reader-tier list_databases tool, which interpolates stateFilter into the query For OS command execution: the SQL login is privileged and xp_cmdshell is enabled

Summary

Several ConnorBritain packages (mssql-mcp-core, mssql-mcp-reader, mssql-mcp-writer, and mssql-mcp-server) build database commands from caller-supplied table names, column names, and filter conditions. A remote attacker with a low-privilege login can send crafted input over the network to read, change, or destroy database data, and potentially run operating-system commands if the SQL login is privileged and xp_cmdshell is enabled.

Original description

mssql-mcp-core is the shared library that powers MSSQL MCP servers. Prior to core and server 0.6.0 and reader and writer 0.5.0, multiple database tools interpolate caller-controlled identifiers and predicates into T-SQL batches passed to Request.query() while parameterizing only data values. update_data, delete_data, insert_data, execute_transaction, create_table, create_index, and drop_table accept unsafe tableName, column, index, schema, or free-form whereClause input, while reader-tier list_databases interpolates stateFilter without runtime allowlist enforcement. Row-count and preview queries execute before confirmUpdate or confirmDelete, allowing malicious arguments to bypass confirmation and maxRows controls and execute stacked DDL or DML, read or destroy data, and potentially run operating-system commands when the SQL login is privileged and xp_cmdshell is enabled. This issue is fixed in core and server version 0.6.0 and reader and writer version 0.5.0.

Who should check

Teams running ConnorBritain mssql-mcp-core, mssql-mcp-reader, mssql-mcp-writer or mssql-mcp-server (npm) MCP servers against SQL Server

Not fixed by: READONLY=true does not block the list_databases stateFilter injection.

“Several tools in mssql-mcp-core built T-SQL by string-interpolating caller-supplied identifiers and predicates”

github.com

cve.now Index

17Pcve.now Index 17 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.8/10CVSS 8.8
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    Uses the update_data, delete_data, insert_data, execute_transaction, create_table, create_index or drop_table tools, which interpolate tableName and whereClause into SQL Uses the reader-tier list_databases tool, which interpolates stateFilter into the query For OS command execution: the SQL login is privileged and xp_cmdshell is enabled
  • Upgrade to a fixed version: mssql-mcp-core 0.6.0 · mssql-mcp-reader 0.5.0 · mssql-mcp-writer 0.5.0 · mssql-mcp-server 0.6.0.

  • Workaround: Run the server under a least-privilege SQL login with xp_cmdshell disabled, and restrict which MCP clients can invoke the tools

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-63129 (mssql-mcp-core: SQL injection in mssql-mcp write tools via unparameterized table names and WHERE clauses), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-63129 (entry last updated 2026-11-18):
Affected:
- ConnorBritain mssql-mcp-core: fixed in 0.6.0
- ConnorBritain mssql-mcp-reader: fixed in 0.5.0
- ConnorBritain mssql-mcp-writer: fixed in 0.5.0
- ConnorBritain mssql-mcp-server: fixed in 0.6.0
Fixed versions: 0.6.0, 0.5.0.
Conditions (all must be true for the bug to be hit):
- Uses the update_data, delete_data, insert_data, execute_transaction, create_table, create_index or drop_table tools, which interpolate tableName and whereClause into SQL (source: https://github.com/ConnorBritain/mssql-mcp-core/security/advisories/GHSA-2m9m-6cr5-9x25)
- Uses the reader-tier list_databases tool, which interpolates stateFilter into the query (source: https://github.com/ConnorBritain/mssql-mcp-core/security/advisories/GHSA-2m9m-6cr5-9x25)
- For OS command execution: the SQL login is privileged and xp_cmdshell is enabled (source: https://github.com/ConnorBritain/mssql-mcp-core/security/advisories/GHSA-2m9m-6cr5-9x25)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
Workaround: Run the server under a least-privilege SQL login with xp_cmdshell disabled, and restrict which MCP clients can invoke the tools (source: https://github.com/ConnorBritain/mssql-mcp-core/security/advisories/GHSA-2m9m-6cr5-9x25)
CISA KEV: CVE-2026-63129 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63129 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/ConnorBritain/mssql-mcp-core/security/advisories/GHSA-2m9m-6cr5-9x25
- https://github.com/ConnorBritain/mssql-mcp-core/pull/1
- https://github.com/ConnorBritain/mssql-mcp-core/commit/227e2efc4e3311c477b7ae509c3ae15437a4f815
- https://github.com/ConnorBritain/mssql-mcp-core/commit/a9727f83768598e4fdbddfbc717ccfebb84ae7af
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-63129
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-63129"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • ConnorBritain mssql-mcp-core

    fixed in 0.6.0

  • ConnorBritain mssql-mcp-reader

    fixed in 0.5.0

  • ConnorBritain mssql-mcp-writer

    fixed in 0.5.0

  • ConnorBritain mssql-mcp-server

    fixed in 0.6.0

Evidence 6

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-63129

Is CVE-2026-63129 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

The mssql-mcp write tools insert the table name and the free-form WHERE clause directly into SQL without parameterization, so crafted input can change the query. The advisory says this could read, modify, or drop arbitrary data, bypass preview and confirmation safeguards, and conditionally execute OS commands.Source: github.com

Which versions are affected by CVE-2026-63129?

mssql-mcp-core: before 0.6.0. mssql-mcp-reader: before 0.5.0. mssql-mcp-writer: before 0.5.0. mssql-mcp-server: before 0.6.0.Source: cve.now feed data

Am I affected, and how do I check?

Affected versions are mssql-mcp-core and mssql-mcp-server before 0.6.0, and mssql-mcp-reader and mssql-mcp-writer before 0.5.0. The issue is in the update_data, delete_data, insert_data, execute_transaction, create_table, create_index, and drop_table tools, and in the reader-tier list_databases tool through its stateFilter argument. OS command execution additionally requires a privileged SQL login with xp_cmdshell enabled, so check the installed package versions and the SQL login's privileges and xp_cmdshell setting.Source: github.com

How do I fix CVE-2026-63129?

Upgrade mssql-mcp-reader and mssql-mcp-writer to 0.5.0, and mssql-mcp-server and mssql-mcp-core to 0.6.0. No patch IDs are listed for this advisory.Source: github.com

More CVEs