VulnerabilityPublished 27 Mar 2026

CVE-2026-33980: pab1it0 adx-mcp-server · Improper Neutralization of Special Elements in Data Query Logic

Affects pab1it0 adx-mcp-serverSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.3 High · patch available : patch pab1it0 adx-mcp-server soon.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

8.3High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 34% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
pab1it0adx-mcp-server	Affected <=1.1.0	Fixed in–
GitHubpab1it0/adx-mcp-server`pkg:github/pab1it0/adx-mcp-server`Other threats	Affected <=1.1.0	Fixed in–

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

AI-suggested

Immediately upgrade the pab1it0 adx-mcp-server to version 1.1.1 or later where the vulnerability is patched.
Implement strict input validation and sanitization on all user-supplied parameters, especially 'table_name', to neutralize special characters and prevent query injection.
Employ least privilege principles for accounts accessing the MCP server to limit potential damage from exploitation.
Monitor and audit KQL query logs for unusual or unauthorized query patterns indicative of injection attempts.
Use network segmentation and firewall rules to restrict access to the MCP server to trusted sources only.
Consider deploying Web Application Firewalls (WAFs) or query filtering mechanisms that can detect and block suspicious KQL injection payloads.
Educate AI assistant developers and operators about the risks of prompt injection and enforce secure coding practices when integrating AI with data query interfaces.
Regularly review and update security policies for AI-driven data access to include threat modeling for injection attacks.

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.

Impact

The primary impact of CVE-2026-33980 is unauthorized access and manipulation of data within Azure Data Explorer clusters. Attackers exploiting this vulnerability can execute arbitrary KQL queries, potentially extracting sensitive information, modifying data, or disrupting data integrity. This can lead to data breaches, exposure of confidential business intelligence, and undermining trust in data accuracy. Since the vulnerability affects AI assistant interfaces, it also raises concerns about automated systems being manipulated to perform malicious queries. The availability impact is limited but could occur if malicious queries degrade cluster performance or cause resource exhaustion. Organizations relying on Azure Data Explorer for critical analytics and decision-making may face operational and reputational damage. The ease of exploitation combined with the high impact on confidentiality and integrity makes this a significant threat to any entity using the affected adx-mcp-server versions.

CWE-943Improper Neutralization of Special Elements in Data Query Logic (opens in a new tab)
Class weakness
The product generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
NoSQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 21:51 UTC

Public exploits and detectionGitHub proofs of concept

WeaknessesCWE-943

Technical details

References

Community reviews

Related threats