Skip to main content
CVE-2026-63129VulnerabilityPublished

mssql-mcp write tools · mssql-mcp-core: SQL injection

Affects @connorbritain/mssql-mcp-coreSource GCVE Database

0
Compare
Authoritative record:CVE-2026-63129· High 8.8

Not known to be exploited · CVSS 8.8 High : upgrade to 0.6.0 soon.

Data as of 19 Nov 2026, 01:50 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.18.8
Patch
Available – fixed in 0.6.0, 0.5.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade @connorbritain/mssql-mcp-core and @connorbritain/mssql-mcp-server to 0.6.0; @connorbritain/mssql-mcp-reader and @connorbritain/mssql-mcp-writer to 0.5.0.

Affected software

ProductAffectedFixed in
npm@connorbritain/mssql-mcp-coreAffected
  • <0.6.0
Fixed in
  • 0.6.0
npm@connorbritain/mssql-mcp-readerAffected
  • <0.5.0
Fixed in
  • 0.5.0
npm@connorbritain/mssql-mcp-writerAffected
  • <0.5.0
Fixed in
  • 0.5.0
npm@connorbritain/mssql-mcp-serverAffected
  • <0.6.0
Fixed in
  • 0.6.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A complete fix is available in mssql-mcp-core version 0.6.0 and related consumer packages (mssql-mcp-reader 0.5.0, mssql-mcp-writer 0.5.0, mssql-mcp-server 0.6.0). Upgrading to these versions is the recommended remediation. As defense in depth, run the server with a least-privilege SQL login and ensure xp_cmdshell is disabled. Restrict which MCP clients can invoke the vulnerable tools. No other workarounds fully mitigate the issue.

Description

The mssql-mcp-core package contained SQL injection vulnerabilities due to unparameterized interpolation of table names, column names, and WHERE clauses in several tools. This allowed attackers supplying crafted inputs to execute arbitrary SQL statements, bypassing safety checks and potentially executing OS commands if the SQL login was privileged and xp_cmdshell enabled. The issue was fixed in version 0.6.0 by validating identifiers against allowlists and replacing free-form WHERE clauses with structured, parameterized filters.

References

Community reviews

Loading reviews…