CVE-2025-27819 Apache Kafka: Possible RCE/Denial of service attack via SASL JAAS JndiLoginModule configuration

High 7.5 Published Updated

Attackers with AlterConfigs permission can trigger RCE or DoS via SASL JAAS JndiLoginModule configuration in Apache Kafka brokers.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2025-27819?

CVE-2025-27819 is a high-severity unsafe deserialization vulnerability in Apache Kafka, published on 10 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

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

Weakness: CWE-502

Which versions are affected by CVE-2025-27819?

17 open source packages ship an affected version, including org.apache.kafka:kafka_2.10, kafka and org.apache.kafka:kafka_2.11. It affects 1 product.

PackageAffectedFixed in
org.apache.kafka:kafka_2.10 MavenAll versionsNone
org.apache.kafka:kafka_2.10 MavenAll versionsNone
kafka BitnamiFrom 2.0.03.4.1
org.apache.kafka:kafka_2.11 MavenAll versionsNone
org.apache.kafka:kafka_2.11 MavenAll versionsNone
org.apache.kafka:kafka_2.12 MavenAll versions3.4.0
11 more packages
org.apache.kafka:kafka_2.12 MavenAll versions3.4.0
org.apache.kafka:kafka_2.13 MavenAll versions3.4.0
org.apache.kafka:kafka_2.13 MavenAll versions3.4.0
org.apache.kafka:kafka_2.8.0 MavenAll versionsNone
org.apache.kafka:kafka_2.8.0 MavenAll versionsNone
org.apache.kafka:kafka_2.8.2 MavenAll versionsNone
org.apache.kafka:kafka_2.8.2 MavenAll versionsNone
org.apache.kafka:kafka_2.9.1 MavenAll versionsNone
org.apache.kafka:kafka_2.9.1 MavenAll versionsNone
org.apache.kafka:kafka_2.9.2 MavenAll versionsNone
org.apache.kafka:kafka_2.9.2 MavenAll versionsNone

Products include Apache Kafka.

How do I fix CVE-2025-27819?

Change a configuration setting.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2025-27819 being exploited?

There is no known exploitation of CVE-2025-27819 in the wild and no public exploit code.

Sources

Also known as BIT-kafka-2025-27819, GHSA-mcwh-c9pg-xw43.

Is CVE-2025-27819 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free