# CVE-2025-27819: Apache Kafka: Possible RCE/Denial of service attack via SASL JAAS JndiLoginModule configuration > Attackers with AlterConfigs permission can trigger RCE or DoS via SASL JAAS JndiLoginModule configuration in Apache Kafka brokers. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 10 Jun 2025 - **Updated:** 10 Jun 2025 - **Also known as:** BIT-kafka-2025-27819, GHSA-mcwh-c9pg-xw43 ## 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 (Deserialization of Untrusted Data) ## 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. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.kafka:kafka_2.10` | Maven | All versions | None | | `org.apache.kafka:kafka_2.10` | Maven | All versions | None | | `kafka` | Bitnami | From 2.0.0 | 3.4.1 | | `org.apache.kafka:kafka_2.11` | Maven | All versions | None | | `org.apache.kafka:kafka_2.11` | Maven | All versions | None | | `org.apache.kafka:kafka_2.12` | Maven | All versions | 3.4.0 | | `org.apache.kafka:kafka_2.12` | Maven | All versions | 3.4.0 | | `org.apache.kafka:kafka_2.13` | Maven | All versions | 3.4.0 | | `org.apache.kafka:kafka_2.13` | Maven | All versions | 3.4.0 | | `org.apache.kafka:kafka_2.8.0` | Maven | All versions | None | | `org.apache.kafka:kafka_2.8.0` | Maven | All versions | None | | `org.apache.kafka:kafka_2.8.2` | Maven | All versions | None | | `org.apache.kafka:kafka_2.8.2` | Maven | All versions | None | | `org.apache.kafka:kafka_2.9.1` | Maven | All versions | None | | `org.apache.kafka:kafka_2.9.1` | Maven | All versions | None | | `org.apache.kafka:kafka_2.9.2` | Maven | All versions | None | | `org.apache.kafka:kafka_2.9.2` | Maven | All versions | None | Products: Apache Kafka. ## How do I fix CVE-2025-27819? Change a configuration setting. ## Is CVE-2025-27819 being exploited? There is no known exploitation of CVE-2025-27819 in the wild and no public exploit code. ## Other vulnerabilities in Apache Kafka - [CVE-2026-33557](https://insights.sbomify.com/CVE-2026-33557/): Apache Kafka: Missing JWT token validation in OAUTHBEARER authentication (critical 9.1) - [CVE-2025-27818](https://insights.sbomify.com/CVE-2025-27818/): Apache Kafka: Possible RCE attack via SASL JAAS LdapLoginModule configuration (high 8.8) - [CVE-2018-17196](https://insights.sbomify.com/CVE-2018-17196/): Improper Input Validation in Apache Kafka (high 8.8) - [CVE-2026-35554](https://insights.sbomify.com/CVE-2026-35554/): Apache Kafka Clients: Kafka Producer Message Corruption and Misrouting via Buffer Pool Race Condition (high 8.7) - [CVE-2025-27817](https://insights.sbomify.com/CVE-2025-27817/): Apache Kafka Client: Arbitrary file read and SSRF vulnerability (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-27819 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2025-27819 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.kafka:kafka_2.10 (Maven): affected all versions; no fix listed - org.apache.kafka:kafka_2.10 (Maven): affected all versions; no fix listed - kafka (Bitnami): affected from 2.0.0; fixed in 3.4.1 - org.apache.kafka:kafka_2.11 (Maven): affected all versions; no fix listed - org.apache.kafka:kafka_2.11 (Maven): affected all versions; no fix listed - org.apache.kafka:kafka_2.12 (Maven): affected all versions; fixed in 3.4.0 - org.apache.kafka:kafka_2.12 (Maven): affected all versions; fixed in 3.4.0 - org.apache.kafka:kafka_2.13 (Maven): affected all versions; fixed in 3.4.0 - org.apache.kafka:kafka_2.13 (Maven): affected all versions; fixed in 3.4.0 - org.apache.kafka:kafka_2.8.0 (Maven): affected all versions; no fix listed - org.apache.kafka:kafka_2.8.0 (Maven): affected all versions; no fix listed - org.apache.kafka:kafka_2.8.2 (Maven): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-27819/ (Markdown: https://insights.sbomify.com/CVE-2025-27819/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-27819 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-27819 - OSV: https://osv.dev/vulnerability/CVE-2025-27819 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-27819/ Summaries are generated and may contain mistakes; the official description above is the record.