CVE-2026-33980
Published: 27 March 2026
Summary
CVE-2026-33980 is a high-severity Improper Neutralization of Special Elements in Data Query Logic (CWE-943) vulnerability in Pab1It0 Azure Data Explorer Mcp Server. Its CVSS base score is 8.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 13.0th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
This vulnerability is AI-related — categorised as AI Agent Protocols and Integrations; in the Protocol-Specific Risks risk domain.
The strongest mitigations our analysis identified are NIST 800-53 SI-10 (Information Input Validation) and SI-2 (Flaw Remediation).
Threat & Defense at a Glance
Threat & Defense Details
Mitigating Controls (NIST 800-53 r5)AI
Directly prevents KQL injection by requiring validation and sanitization of the table_name parameter before interpolating it into queries in the affected MCP tool handlers.
Mandates timely remediation of the specific KQL injection flaws in get_table_schema, sample_table_data, and get_table_details via patching as in commit 0abe0ee55279e111281076393e5e966335fffd30.
Facilitates detection of exploitation by monitoring for indicators of anomalous KQL query executions triggered by malicious table_name inputs.
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
KQL injection in the exposed MCP server handlers directly enables exploitation of a public-facing application (T1190) to achieve arbitrary query execution against Azure Data Explorer, facilitating data access from databases (T1213.006) and stored data manipulation (T1565.001).
NVD Description
Azure Data Explorer MCP Server is a Model Context Protocol (MCP) server that enables AI assistants to execute KQL queries and explore Azure Data Explorer (ADX/Kusto) databases through standardized interfaces. Versions up to and including 0.1.1 contain KQL (Kusto Query…
more
Language) injection vulnerabilities in three MCP tool handlers: `get_table_schema`, `sample_table_data`, and `get_table_details`. The `table_name` parameter is interpolated directly into KQL queries via f-strings without any validation or sanitization, allowing an attacker (or a prompt-injected AI agent) to execute arbitrary KQL queries against the Azure Data Explorer cluster. Commit 0abe0ee55279e111281076393e5e966335fffd30 patches the issue.
Deeper analysisAI
Azure Data Explorer MCP Server, a Model Context Protocol (MCP) server that allows AI assistants to execute KQL queries and explore Azure Data Explorer (ADX/Kusto) databases via standardized interfaces, contains KQL injection vulnerabilities in versions up to and including 0.1.1. The flaws affect three MCP tool handlers—get_table_schema, sample_table_data, and get_table_details—where the table_name parameter is directly interpolated into KQL queries using f-strings without validation or sanitization. This enables attackers to inject and execute arbitrary KQL queries against the connected Azure Data Explorer cluster. The vulnerability is rated with a CVSS v3.1 base score of 8.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L) and is associated with CWE-943.
Attackers with low privileges (PR:L) can exploit this over the network with low complexity and no user interaction required. Exploitation occurs by supplying a malicious table_name value, potentially through direct access to the MCP server or via a prompt-injected AI agent interacting with the tools. Successful attacks allow arbitrary KQL query execution, enabling high confidentiality and integrity impacts such as data exfiltration, modification, or limited denial of service, depending on the attacker's permissions within the Azure Data Explorer cluster.
The patching commit 0abe0ee55279e111281076393e5e966335fffd30 addresses the issue by fixing the injection flaws in the affected handlers. Security practitioners should update to a version incorporating this commit, as detailed in the GitHub security advisory GHSA-vphc-468g-8rfp.
This vulnerability has particular relevance to AI/ML deployments, as it targets an MCP server designed for AI assistants, highlighting risks of prompt injection leading to database compromise in agentic AI workflows. No public evidence of real-world exploitation is available as of publication on 2026-03-27.
Details
- CWE(s)
Affected Products
AI Security AnalysisAI
- AI Category
- AI Agent Protocols and Integrations
- Risk Domain
- Protocol-Specific Risks
- OWASP Top 10 for LLMs 2025
- None mapped
- Classification Reason
- Matched keywords: mcp, model context protocol, mcp, ai, mcp, ai