CVE-2025-27819: Apache Kafka: Possible RCE/Denial of service attack via SASL JAAS JndiLoginModule configuration
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.
Since Apache Kafka 3.4.0, we have added a system property ("-Dorg.apache.kafka.disallowed.login.modules") to disable the problematic login modules usage in SASL JAAS configuration. Also by default "com.sun.security.auth.module.JndiLoginModule" is disabled in Apache Kafka 3.4.0, and "com.sun.security.auth.module.JndiLoginModule,com.sun.security.auth.module.LdapLoginModule" is disabled by default in in Apache Kafka 3.9.1/4.0.0
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-27819?
CVE-2025-27819 is considered to have a high severity due to its potential for remote code execution and denial of service attacks.
How do I fix CVE-2025-27819?
To fix CVE-2025-27819, upgrade to Apache Kafka version 3.4.0 or later.
Which Apache Kafka versions are affected by CVE-2025-27819?
CVE-2025-27819 affects all Apache Kafka versions prior to 3.4.0.
What types of attacks can be launched due to CVE-2025-27819?
CVE-2025-27819 can be exploited for remote code execution and denial of service attacks.
Is the Kafka Connect API affected by CVE-2025-27819?
Yes, both the Kafka Connect API and Apache Kafka brokers are vulnerable to CVE-2025-27819.