<?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>Wed, 07 Oct 2026 08:41:29 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-27819 — Apache Kafka: Possible RCE/Denial of service attack via SASL JAAS JndiLoginModule configuration</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-27819</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Kafka&lt;/p&gt;
&lt;p&gt;In CVE-2023-25194, we announced the RCE/Denial of service attack via SASL JAAS JndiLoginModule configuration in Kafka Connect API. But not only Kafka Connect API is vulnerable to this attack, the Apache Kafka brokers also have this vulnerability. To exploit this vulnerability, the attacker needs to be able to connect to the Kafka cluster and have the AlterConfigs permission on the cluster resource.&lt;/p&gt;
&lt;p&gt;Since Apache Kafka 3.4.0, we have added a system property (&amp;#34;-Dorg.apache.kafka.disallowed.login.modules&amp;#34;) to disable the problematic login modules usage in SASL JAAS configuration. Also by default &amp;#34;com.sun.security.auth.module.JndiLoginModule&amp;#34; is disabled in Apache Kafka 3.4.0, and &amp;#34;com.sun.security.auth.module.JndiLoginModule,com.sun.security.auth.module.LdapLoginModule&amp;#34; is disabled by default in in Apache Kafka 3.9.1/4.0.0&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Apache Software Foundation Apache Kafka&lt;/p&gt;
&lt;p&gt;In CVE-2023-25194, we announced the RCE/Denial of service attack via SASL JAAS JndiLoginModule configuration in Kafka Connect API. But not only Kafka Connect API is vulnerable to this attack, the Apache Kafka brokers also have this vulnerability. To exploit this vulnerability, the attacker needs to be able to connect to the Kafka cluster and have the AlterConfigs permission on the cluster resource.&lt;/p&gt;
&lt;p&gt;Since Apache Kafka 3.4.0, we have added a system property (&amp;#34;-Dorg.apache.kafka.disallowed.login.modules&amp;#34;) to disable the problematic login modules usage in SASL JAAS configuration. Also by default &amp;#34;com.sun.security.auth.module.JndiLoginModule&amp;#34; is disabled in Apache Kafka 3.4.0, and &amp;#34;com.sun.security.auth.module.JndiLoginModule,com.sun.security.auth.module.LdapLoginModule&amp;#34; is disabled by default in in Apache Kafka 3.9.1/4.0.0&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-27819</guid>
    </item>
  </channel>
</rss>
