Skip to main content
No exploitation reportedFix available

CVE-2025-27819

No exploitation reported by the sources we read.

  • Published2025-06-10
  • Fixed in3.4.1
  • WeaknessCWE-502

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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

Timeline

dates in UTC
  1. 2025-06-1008:15CVE publishedNVD

Versions per branch

OSV · NVD
kafka
BranchAffectedFixed in
3.4≥ 2.0.0, < 3.4.13.4.1
Apache kafka
BranchAffectedFixed in
3.3≥ 2.0.0, ≤ 3.3.2no fix published
kafka_2.10
BranchAffectedFixed in
—all versionsno fix published

7 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As apache, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • Apache Software Foundation Apache Kafkaother versions: not affected
    Affected
    • ≥ 2.0.0, ≤ 3.3.2no fix statedsemver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2025-06-10

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • kafkaopenEuler:24.03-LTS-SP4all versions · fixed in 2.8.2-21.oe2403sp4
  • kafkaopenEuler:24.03-LTS-SP3all versions · fixed in 2.8.2-21.oe2403sp3
  • kafkaopenEuler:24.03-LTS-SP1all versions · fixed in 2.8.2-21.oe2403sp1
  • kafkaopenEuler:22.03-LTS-SP4all versions · fixed in 2.8.2-3.oe2203sp4
  • org.apache.kafka:kafka_2.12TuxCare:Mavenfrom 3.2.3 · fixed in 3.2.3.tuxcare.1and 2 other packages

Vendor advisories

  • CVE-2025-27819 Red Hat Product Security1 product fixed

    org.apache.kafka: Kafka JNDI Login Module RCE Vulnerability

  • RHSA-2025:23417 Red Hat Product Security1 product fixed

    Red Hat Security Advisory: Streams for Apache Kafka 3.1.0 release and security update

Full record on NVD

Fix

  1. Update kafka to 3.4.1
  2. Vendor fix Red Hat Product Security RHSA-2025:23417 · 1 productBefore applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
  3. Workaround from the vendor Red Hat Product Security RHSA-2025:23417 · 1 productTo 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".

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2025-06-10
Last Modified
2026-06-17
NVD status
Analyzed
GitHub Advisory
GHSA-mcwh-c9pg-xw43

Frequently asked questions

What is CVE-2025-27819?

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

Is CVE-2025-27819 actively exploited?

Active exploitation of CVE-2025-27819 has not been confirmed. Its EPSS score was 1.1% on 2026-11-18, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2025-27819?

CVE-2025-27819 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running kafka? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record