NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

CVE-2025-27819 — kafka_2.10

HIGH

CVE-2025-27819 is a high-severity (CVSS 7.5) Deserialization of Untrusted Data vulnerability in org.apache.kafka:kafka_2.10. A fix is available for org.apache.kafka:kafka_2.10 — see the affected versions and patch details below.

Apache Kafka: Possible RCE/Denial of service attack via SASL JAAS JndiLoginModule configuration

Also known asBIT-kafka-2025-27819GHSA-mcwh-c9pg-xw43
Published
Updated
Affected
8 pkgs
Patched
2 / 8
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-27819.

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk+0.08%
Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk
0.37%0.78%1.19%1.61%0.9%1.1%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

8 pkgs affected
☕org.apache.kafka:kafka_2.10☕org.apache.kafka:kafka_2.11☕org.apache.kafka:kafka_2.12☕org.apache.kafka:kafka_2.13☕org.apache.kafka:kafka_2.8.0☕org.apache.kafka:kafka_2.8.2☕org.apache.kafka:kafka_2.9.1☕org.apache.kafka:kafka_2.9.2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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

Affected Packages

8 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.apache.kafka:kafka_2.10all versionsNo fix
☕Mavenorg.apache.kafka:kafka_2.11all versionsNo fix
☕Mavenorg.apache.kafka:kafka_2.12all versions3.4.0org.apache.kafka:kafka_2.12:3.4.0
☕Mavenorg.apache.kafka:kafka_2.13all versions3.4.0org.apache.kafka:kafka_2.13:3.4.0
☕Mavenorg.apache.kafka:kafka_2.8.0all versionsNo fix
☕Mavenorg.apache.kafka:kafka_2.8.2all versionsNo fix

Affected Products

1 product · 1 configurations
Application
kafkaapache
≥ 2.0.0 && ≤ 3.3.2
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.kafka:kafka_2.10, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    A fix is available for CVE-2025-27819; check the affected-versions list above or the advisory for the patched release of org.apache.kafka:kafka_2.10, then make sure no transitive dependency still pins the vulnerable range.

  3. Workarounds

    Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

No Red Hat products or offerings are affected by this vulnerability. This vulnerability is categorized as Important rather than Moderate due to its potential to enable remote code execution (RCE) or denial of service (DoS) in a core component of Apache Kafka—its brokers—under certain but realistic conditions. While…

Workaround published by Red Hat
To mitigate this flaw, disable the problematic login module's usage in the SASL JAAS configuration using the system property, "-Dorg.apache.kafka.disallowed.login.modules".
Source: Red Hat security advisory for CVE-2025-27819 (CC BY 4.0)
ProductFixed inAdvisory
Streams for Apache Kafka 3.1.0kafkaRHSA-2025:23417

Frequently Asked Questions

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
O3 Security · Impact-Aware SCA

Is CVE-2025-27819 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2025-27819: kafka_2.10 RCE — Fixed in 3.4.0