cve.bz

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

8.8 highEPSS 0.6%Fix available

High (8.8) in connorbritain. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in @connorbritain/mssql-mcp-core 0.6.0.

On this page
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.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.6% estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-89 Improper Neutralization of Special Elements used in an SQL Command (SQL Injection)
OWASP Top 10
A05:2025 Injection
Published
Assigned by
GitHub_M (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • @connorbritain/mssql-mcp-core (npm): fixed in 0.6.0
  • @connorbritain/mssql-mcp-reader (npm): fixed in 0.5.0
  • @connorbritain/mssql-mcp-writer (npm): fixed in 0.5.0
  • @connorbritain/mssql-mcp-server (npm): fixed in 0.6.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-63129 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-63129?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-63129?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-63129 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
ConnorBritain mssql-mcp-core< 0.6.0
ConnorBritain mssql-mcp-reader< 0.5.0
ConnorBritain mssql-mcp-writer< 0.5.0
ConnorBritain mssql-mcp-server< 0.6.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-2m9m-6cr5-9x25npm@connorbritain/mssql-mcp-core<0.6.00.6.0
GHSA-2m9m-6cr5-9x25npm@connorbritain/mssql-mcp-reader<0.5.00.5.0
GHSA-2m9m-6cr5-9x25npm@connorbritain/mssql-mcp-writer<0.5.00.5.0
GHSA-2m9m-6cr5-9x25npm@connorbritain/mssql-mcp-server<0.6.00.6.0

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • LLCForge/CVE-2026-63129 Harbor Check: matches CVE 0 stars, Python, created
    @connorbritain/mssql-mcp-core (npm) — SQL injection via unparameterized table names and WHERE clauses in write tools. High.

Attack patterns (CAPEC)

  • CAPEC-7 Blind SQL Injection Likelihood: High · Severity: High
  • CAPEC-66 SQL Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High
  • CAPEC-109 Object Relational Mapping Injection Likelihood: Low · Severity: High
  • CAPEC-110 SQL Injection through SOAP Parameter Tampering Likelihood: High · Severity: Very High
  • CAPEC-470 Expanding Control over the Operating System from the Database Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON