# CVE-2026-33980: Azure Data Explorer MCP Server: KQL Injection in multiple tools allows MCP client to execute arbitrary Kusto queries

> Attackers can execute arbitrary Kusto queries via KQL injection in Azure Data Explorer MCP Server tools, potentially reading or modifying database contents.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2026
- **Updated:** 27 Mar 2026
- **Also known as:** GHSA-vphc-468g-8rfp, PYSEC-2026-2327

## What is CVE-2026-33980?

CVE-2026-33980 is a high-severity code injection vulnerability in pab1it0 adx-mcp-server, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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 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.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

## Which versions are affected by CVE-2026-33980?

3 open source packages ship an affected version, including adx-mcp-server. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `adx-mcp-server` | PyPI | All versions to 1.1.0 | None |
| `adx-mcp-server` | PyPI | All versions to 1.1.0 | None |
| `adx-mcp-server` | PyPI | All versions to 1.1.0 | None |

Products: Pab1it0 Azure Data Explorer Mcp Server.

## How do I fix CVE-2026-33980?

No fix has been published for CVE-2026-33980 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33980 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33980 exists.

Public exploit code:

- KQL injection in adx-mcp-server via table_name — CVE-2026-33980 / CVSS 8.3 (github_poc): https://github.com/romain-deperne/CVE-2026-33980

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33980 and fix it if it is affected.

What it is: CVE-2026-33980 is a high-severity code injection vulnerability in pab1it0 adx-mcp-server, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33980 exists.

Affected packages and fixed versions:
- adx-mcp-server (PyPI): affected all versions up to 1.1.0; no fix listed
- adx-mcp-server (PyPI): affected all versions up to 1.1.0; no fix listed
- adx-mcp-server (PyPI): affected all versions up to 1.1.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33980/ (Markdown: https://insights.sbomify.com/CVE-2026-33980/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33980
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33980
- OSV: https://osv.dev/vulnerability/CVE-2026-33980

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33980/
Summaries are generated and may contain mistakes; the official description above is the record.