CVE-2026-63129
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 (
Properties
- Summary
- mssql-mcp-core: SQL injection in mssql-mcp write tools via unparameterized table names and WHERE clauses
- Severity
- high
- Nvd fetched at
- 2026-11-19T03:31:17.617109+00:00
- Cvss score
- 8.8
- Cvss severity
- HIGH
- Retrieved at
- 2026-11-19T03:32:39+00:00
- Ghsa published
- 2026-11-19T00:46:38Z
- Source url
- https://github.com/advisories/GHSA-2m9m-6cr5-9x25
- Ghsa updated
- 2026-11-19T00:46:41Z
- Ghsa id
- GHSA-2m9m-6cr5-9x25
- Last source
- GitHub Advisory Database
- Score
- 8.8
- Cvss version
- 3.1
- Cve id
- CVE-2026-63129
- Cvss vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- First seen by Signal
- 2026-11-18T23:15:15+00:00
- Name
- CVE-2026-63129
- Is ghsa only
- false
- Vector
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published at
- 2026-11-18T20:19:10.557
Related Entities (9)
AFFECTS (4)
VULNERABLE_TO (4)
HAS_WEAKNESS (1)
Related research
Explore deeper with Ninja Signal's threat intelligence graph