cve.bz

CVE-2025-27818 apache kafka: Deserialization of Untrusted Data

8.8 highEPSS 1.1%Fix available

High (8.8) in apache kafka. EPSS 1.1% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.kafka:kafka_2.12 3.9.1.

On this page
A possible security vulnerability has been identified in Apache Kafka. This requires access to a alterConfig to the cluster resource, or Kafka Connect worker, and the ability to create/modify connectors on it with an arbitrary Kafka client SASL JAAS config and a SASL-based security protocol, which has been possible on Kafka clusters since Apache Kafka 2.0.0 (Kafka Connect 2.3.0). When configuring the broker via config file or AlterConfig command, or connector via the Kafka Kafka Connect REST API, an authenticated operator can set the `sasl.jaas.config` property for any of the connector's Kafka clients to "com.sun.security.auth.module.LdapLoginModule", which can be done via the `producer.override.sasl.jaas.config`, `consumer.override.sasl.jaas.config`, or `admin.override.sasl.jaas.config` properties. This will allow the server to connect to the attacker's LDAP server and deserialize the LDAP response, which the attacker can use to execute java deserialization gadget chains on the Kafka connect server. Attacker can cause unrestricted deserialization of untrusted data (or) RCE vulnerability when there are gadgets in the classpath. Since Apache Kafka 3.0.0, users are allowed to specify these properties in connector configurations for Kafka Connect clusters running with out-of-the-box configurations. Before Apache Kafka 3.0.0, users may not specify these properties unless the Kafka Connect cluster has been reconfigured with a connector client override policy that permits them. Since Apache Kafka 3.9.1/4.0.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,com.sun.security.auth.module.LdapLoginModule" are disabled in Apache Kafka Connect 3.9.1/4.0.0. We advise the Kafka users to validate connector configurations and only allow trusted LDAP configurations. Also examine connector dependencies for vulnerable versions and either upgrade their connectors, upgrading that specific dependency, or removing the connectors as options for remediation. Finally, in addition to leveraging the "org.apache.kafka.disallowed.login.modules" system property, Kafka Connect users can also implement their own connector client config override policy, which can be used to control which Kafka client properties can be overridden directly in a connector config and which cannot.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
1.1% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 68th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2025-08-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2025-27818 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-27818?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-27818?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-27818 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Kafkafrom 2.3.0 through 3.9.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-76qp-h5mr-frr4Mavenorg.apache.kafka:kafka_2.11>=2.3.0 <=2.4.1no fix published
GHSA-76qp-h5mr-frr4Mavenorg.apache.kafka:kafka_2.12>=2.3.0 <3.9.13.9.1
GHSA-76qp-h5mr-frr4Mavenorg.apache.kafka:kafka_2.13>=2.4.0 <3.9.13.9.1

Red Hat

Red Hat rates this Important.

Red Hat's statement

No Red Hat products are affected by this flaw.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread

installation base or stability.

ProductPackageStateAdvisory
Streams for Apache Kafka 3.1.0kafkaFixed 2025-12-16RHSA-2025:23417
A-MQ Clients 2kafka-clientsNot affected
Logging Subsystem for Red Hat OpenShiftkafka_2.11Not affected
Logging Subsystem for Red Hat OpenShiftkafka-clientsNot affected
OpenShift Serverlessopenshift-serverless-1/kn-ekb-dispatcher-rhel8Not affected
OpenShift Serverlessopenshift-serverless-1/kn-ekb-kafka-controller-rhel8Not affected
OpenShift Serverlessopenshift-serverless-1/kn-ekb-post-install-rhel8Not affected
OpenShift Serverlessopenshift-serverless-1/kn-ekb-receiver-rhel8Not affected
OpenShift Serverlessopenshift-serverless-1/kn-ekb-webhook-kafka-rhel8Not affected
OpenShift Serverlessopenshift-serverless-1/kn-eventing-istio-controller-rhel8Not affected
Red Hat build of Apache Camel 4 for Quarkus 3quarkus-camel-bomNot affected
Red Hat build of Apache Camel 4 for Quarkus 3quarkus-cxf-bomNot affected
Red Hat build of Apache Camel for Spring Boot 4connect-apiNot affected
Red Hat build of Apache Camel for Spring Boot 4connect-fileNot affected
Red Hat build of Apache Camel for Spring Boot 4connect-jsonNot affected
Red Hat build of Apache Camel for Spring Boot 4connect-runtimeNot affected
Red Hat build of Apache Camel for Spring Boot 4connect-transformsNot affected
Red Hat build of Apache Camel for Spring Boot 4kafka_2.13Not affected
Red Hat build of Apache Camel for Spring Boot 4kafka-clientsNot affected
Red Hat build of Apache Camel for Spring Boot 4kafka-group-coordinatorNot affected
356 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2025-27818.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON