CVE-2023-25194
HighExploitedPublic exploitApache Kafka Connect vulnerable to Deserialization of Untrusted Data
Published Feb 7, 2023 · Updated Jul 7, 2025 · Also known as GHSA-26f8-x7cc-wqpc, TR-23-0072
Key Facts
Patch immediately- CVE-2023-25194 is a high-severity vulnerability (CVSS 8.8 v3.1) affecting Kafka Connect (Apache), org.apache.kafka:connect (maven), kafka (photon) and 1 more product.
- It is exploited in the wild, listed in Industry KEV feed since May 10, 2024. Public exploit code is available.
- EPSS estimates a 96% probability of exploitation in the next 30 days.
- Fixed versions are available, including Kafka Connect <=3.3.2, Apache Kafka Connect API 3.4.0, kafka 3.4.0-1.ph3.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
8.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
96%
Higher than 99.8% of all scored CVEs
Exploited in the wild
Yes
1 catalog listing
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2023-25194 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
A possible security vulnerability has been identified in Apache Kafka Connect API. This requires access to a 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 Connect clusters since Apache Kafka Connect 2.3.0. When configuring the connector via the 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.JndiLoginModule", 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.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 Connect 3.4.0.
We advise the Kafka Connect users to validate connector configurations and only allow trusted JNDI 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.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| Industry KEV feed | May 10, 2024 | n/a | Not reported |
Required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Affected Products
6 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| Kafka ConnectApache | See advisory | 3.3.2 |
| org.apache.kafka:connectmaven | >= 2.3.0 | 3.4.0 |
| kafkaphoton | See advisory | 3.4.0-1.ph3 |
| Apache Kafka Connect API | >= 2.3.0 | 3.4.0 |
Patched Releases
Kafka Connect
<=3.3.2
Apache Kafka Connect API
3.4.0
kafka
3.4.0-1.ph3, 3.4.0-1.ph4, 3.4.0-1.ph5
org.apache.kafka:connect
3.4.0
Timeline
Publicly disclosed
Feb 7, 2023
Added to Industry KEV feed
May 10, 2024
Last updated
Jul 7, 2025
Weakness Type
- CWE-502 Deserialization of Untrusted Data
References
- advisoryRHSA-2023:1241
- advisoryRHSA-2023:3223
- advisoryGHSA advisory
- advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2023-25194
- advisoryhttps://www.cve.org/CVERecord?id=CVE-2023-25194
FAQ
Common Questions.
A possible security vulnerability has been identified in Apache Kafka Connect API.
Affected: Kafka Connect (Apache); org.apache.kafka:connect (maven) versions >= 2.3.0; kafka (photon), among others. The full list is in the CVE brief.
It is exploited in the wild, listed in Industry KEV feed since May 10, 2024.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
Public exploit code is available.
Fixed versions are available, including Kafka Connect <=3.3.2, Apache Kafka Connect API 3.4.0, kafka 3.4.0-1.ph3.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2023-25194 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo