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

High CVSS 8.8

OSV id
GHSA-2m9m-6cr5-9x25
Also known as
CVE-2026-63129
Published
Last modified

Affected packages

PackageAffected versionsFixed in
@connorbritain/mssql-mcp-core
npm
< 0.6.0 0.6.0
@connorbritain/mssql-mcp-reader
npm
< 0.5.0 0.5.0
@connorbritain/mssql-mcp-writer
npm
< 0.5.0 0.5.0
@connorbritain/mssql-mcp-server
npm
< 0.6.0 0.6.0

How to fix it

@connorbritain/mssql-mcp-core (npm)

Upgrade @connorbritain/mssql-mcp-core to 0.6.0 or later.

npm install @connorbritain/mssql-mcp-core@0.6.0
# if it is an indirect dependency: npm update @connorbritain/mssql-mcp-core (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

@connorbritain/mssql-mcp-reader (npm)

Upgrade @connorbritain/mssql-mcp-reader to 0.5.0 or later.

npm install @connorbritain/mssql-mcp-reader@0.5.0
# if it is an indirect dependency: npm update @connorbritain/mssql-mcp-reader (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

@connorbritain/mssql-mcp-writer (npm)

Upgrade @connorbritain/mssql-mcp-writer to 0.5.0 or later.

npm install @connorbritain/mssql-mcp-writer@0.5.0
# if it is an indirect dependency: npm update @connorbritain/mssql-mcp-writer (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

@connorbritain/mssql-mcp-server (npm)

Upgrade @connorbritain/mssql-mcp-server to 0.6.0 or later.

npm install @connorbritain/mssql-mcp-server@0.6.0
# if it is an indirect dependency: npm update @connorbritain/mssql-mcp-server (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

Several tools in mssql-mcp-core built T-SQL by string-interpolating caller-supplied identifiers and predicates directly into the statement passed to the node-mssql Request.query() batch API. Only data values were parameterized.

Affected tools and inputs:

  • update_data, delete_data: tableName and the free-form whereClause were interpolated raw.
  • insert_data: tableName and column names (object keys) were interpolated raw.
  • execute_transaction: the same raw tableName/whereClause interpolation per operation.
  • create_table, create_index, drop_table: table/column/index/schema identifiers were interpolated with no or insufficient validation.
  • list_databases (reader tier): the stateFilter argument was interpolated raw into the query, with only a non-enforced inputSchema enum guarding it.

The only check on whereClause was that it was non-empty. Because the row-count and preview queries run before the confirmUpdate/confirmDelete step, a malicious whereClause or tableName executed on the first call, bypassing the preview/confirmation and maxRows safety controls. Request.query() submits a multi-statement T-SQL batch, so a crafted input enabled stacked statements (arbitrary DDL/DML), sub-selects, and (with a privileged login and xp_cmdshell enabled) OS command execution. Because list_databases is a read-only tool, the stateFilter sink makes the reader package injectable as well.

Impact

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.

Patches

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).

Workarounds

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.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.