<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 15:11:39 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-309978</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309978</link>
      <description>EUVD-2026-309978</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309978</guid>
    </item>
    <item>
      <title>fkie_cve-2026-42316</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-42316</link>
      <description>&lt;p&gt;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) → &amp;#34;&amp;lt;table&amp;gt; | count&amp;#34;, FETCH_TABLE_MAPPING_COMMAND.formatted(table, format, mapping) → &amp;#34;.show table &amp;lt;table&amp;gt; ingestion &amp;lt;format&amp;gt; mapping &amp;#39;&amp;lt;mapping&amp;gt;&amp;#39;&amp;#34;). 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 (;, |, &amp;#39;) to execute arbitrary management commands in the context of the connector&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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) → &amp;#34;&amp;lt;table&amp;gt; | count&amp;#34;, FETCH_TABLE_MAPPING_COMMAND.formatted(table, format, mapping) → &amp;#34;.show table &amp;lt;table&amp;gt; ingestion &amp;lt;format&amp;gt; mapping &amp;#39;&amp;lt;mapping&amp;gt;&amp;#39;&amp;#34;). 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 (;, |, &amp;#39;) to execute arbitrary management commands in the context of the connector&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-42316</guid>
    </item>
  </channel>
</rss>
