CVE-2026-42316
MEDIUMDescription
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) → " | count", FETCH_TABLE_MAPPING_COMMAND.formatted(table, format, mapping) → ".show 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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 27% of all known CVEs.
References
Related Vulnerabilities
Other CWE-943 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-12904 | High | 8.8 | 6.4% | - | Fix |
| CVE-2020-36195 | Critical | 9.8 | 1.8% | - | Fix |
| CVE-2018-7829 | High | 8.8 | 1.7% | - | Fix |
| CVE-2021-1349 | Medium | 6.5 | 1.4% | - | Fix |
| CVE-2018-19952 | High | 7.5 | 1.3% | - | Fix |
| CVE-2022-36084 | Critical | 9.9 | 1.2% | - | Fix |
Common questions
How do I fix CVE-2026-42316?
No published fix for CVE-2026-42316 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-42316 being actively exploited?
Not that we know of. CVE-2026-42316 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.34% is the estimated probability that it will be exploited in the next 30 days. That is higher than 27% of all scored CVEs.
How severe is CVE-2026-42316?
CVE-2026-42316 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-42316
Markdown
[](https://tridentstack.com/cve/CVE-2026-42316)HTML
<a href="https://tridentstack.com/cve/CVE-2026-42316"><img src="https://tridentstack.com/cve/badge/CVE-2026-42316.svg" alt="CVE-2026-42316"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-05-13.