Prior to version 5.2.3, the Kafka Connect plugin for Azure Data Explorer did not sanitize user‑controlled configuration values in the kusto.tables.topics.mapping setting. The plugin used Java String.format to interpolate table, mapping and format fields directly into KQL management commands such as FETCH_TABLE_COMMAND and FETCH_TABLE_MAPPING_COMMAND. Because of this, an attacker who could influence the connector configuration could inject KQL metacharacters, causing arbitrary management commands to be executed in the context of the connector’s service principal. The attacker could enumerate and alter schemas, tamper with ingestion mappings, or modify streaming and retention policies, representing a tampering vulnerability.

This issue affects Azure’s kafka‑sink‑azure‑kusto Kafka Connect sink plugin for Azure Data Explorer. All releases earlier than 5.2.3 are vulnerable. Versions 5.2.3 and later contain the fix that sanitizes configuration input.

The CVSS score is 5.9, indicating moderate severity. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. Exploitation requires an attacker with the ability to modify connector configuration; no external end‑user interaction or record payload is involved. The attack vector is therefore limited to privileged configuration changes within a Kafka Connect deployment.