{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-42316 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-42316 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-42316 is a medium-severity code injection vulnerability in kafka-sink-azure-kusto, published on 11 May 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-42316 and fix it if it is affected.\n\nWhat it is: CVE-2026-42316 is a medium-severity code injection vulnerability in kafka-sink-azure-kusto, published on 11 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-42316 in the wild and no public exploit code.\n\nAffected product: kafka-sink-azure-kusto. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-42316/ (Markdown: https://insights.sbomify.com/CVE-2026-42316/index.md)","id":"CVE-2026-42316","markdown":"https://insights.sbomify.com/CVE-2026-42316/index.md","name":"CVE-2026-42316","record":{"aliases":["GHSA-c9mr-mqvh-6wgj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Kafka Connect plugin","requires_auth":"high_privilege","summary":"Privileged users can inject KQL commands via connector configuration to tamper with Azure Data Explorer schemas and policies.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"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","version":"3.1"},"cwes":[{"id":"CWE-943","name":"Improper Neutralization of Special Elements in Data Query Logic"}],"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) → \"\u003ctable\u003e | count\", FETCH_TABLE_MAPPING_COMMAND.formatted(table, format, mapping) → \".show table \u003ctable\u003e ingestion \u003cformat\u003e mapping '\u003cmapping\u003e'\"). 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"KQL injection via kusto.tables.topics.mapping in kafka-sink-azure-kusto","id":"CVE-2026-42316","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"GLPI vulnerable to arbitrary files deletion by technician","id":"CVE-2026-42317"},"packages":[],"prev":{"headline":"pyLoad: Path Traversal via Package Folder Name in set_package_data","id":"CVE-2026-42315"},"products":["kafka-sink-azure-kusto"],"published":"2026-05-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Azure"]},"summary":"Privileged users can inject KQL commands via connector configuration to tamper with Azure Data Explorer schemas and policies.","url":"https://insights.sbomify.com/CVE-2026-42316/"}