Skip to main content
VulnerabilityPublished

CVE-2026-42316: kafka-sink-azure-kusto · Improper Neutralization of Special Elements in Data Query Logic

Affects kafka-sink-azure-kustoSource CVE Database V5

0
Compare

Public exploit available · CVSS 5.9 Medium : upgrade to 5.2.3 as a priority.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.2.3
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N/E:P/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade kafka-sink-azure-kusto and azure/kafka-sink-azure-kusto to 5.2.3.

Affected software

ProductAffectedFixed in
Azurekafka-sink-azure-kustoAffected
  • <5.2.3
Fixed in
  • 5.2.3
GitHubazure/kafka-sink-azure-kustopkg:github/azure/kafka-sink-azure-kustoOther threatsAffected
  • <5.2.3
Fixed in
  • 5.2.3

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

AI-suggested

An official fix is available in kafka-sink-azure-kusto version 5.2.3. Users should upgrade to this version or later to remediate the vulnerability. Since this is a cloud-hosted service, the vendor manages remediation for the service; users should verify with the vendor advisory that their environment is updated. No additional mitigation actions are required beyond applying the official fix.

Description

kafka-sink-azure-kusto Kafka Connect plugin is the official Microsoft sink for Azure Data Explorer (Kusto). Prior to 5.2.3, kafka-sink-azure-kusto did not sanitize user-controlled values inside the kusto.tables.topics.mapping configuration. The db, table, mapping, and format fields of each mapping entry were interpolated directly into KQL management/query commands via String.formatted(...) (e.g., FETCH_TABLE_COMMAND.formatted(table) → "<table> | count", FETCH_TABLE_MAPPING_COMMAND.formatted(table, format, mapping) → ".show table <table> ingestion <format> mapping '<mapping>'"). An actor able to influence the connector configuration (for example, someone with permissions to submit or edit Kafka Connect connector configs) could embed KQL metacharacters (;, |, ') to execute arbitrary management commands in the context of the connector's service principal — enabling schema enumeration/modification, ingestion-mapping tampering, or changes to streaming/retention policies on the target Azure Data Explorer database. This is a tampering vulnerability. Exploitation requires privileged access to the connector configuration; no end-user interaction or Kafka record payload is involved. This vulnerability is fixed in 5.2.3.

References

Community reviews

Loading reviews…