CVE-2025-27818
No source can show you its own past. This one can.
Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.
Apache Kafka: Possible RCE attack via SASL JAAS LdapLoginModule configuration
rank 2 = 0 + 0 + 0 + 2 + 0
rank@v1 · backlog
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.01041 · without this subject the record ranks 2
What it costs you if it fires
NVD CVSS base score, then the CNA's own
no CVSS held by anyone · without this subject the record ranks 2
It is getting worse, not staying still
FIRST EPSS series, rescorings and bad loads removed
no persisting rise in 365 days · without this subject the record ranks 2
How much of the world it touches
NVD CPE configurations
1 product in the CPE ranges · without this subject the record ranks 0
Someone else already set the date
CISA KEV remediation due date
no CISA due date · without this subject the record ranks 2
Hindsight · the state
Foresight · where to check next
This record is one instance of CWE-502, deserialization of untrusted data. The index holds 3288 prior instances of this class, 76 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1
Running Apache Kafka? Check your version
A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.
Watch this record
Matches your own product list against every record this index holds, and tells you when one of them moves.
Set up a watchlist (needs a Practitioner account)
Record your call
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
AcceptDeferPatch by…Not affectedMitigatedChoose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.
Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.
Harm, if it fires from the vector and the weakness
Written for the ticket you're about to file.
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Exploit Status & Known PoCs a ladder, not a score
Current rung: Nothing observed in held sources.
- RUNG 1Nothing observed in held sources
- RUNG 2Proof-of-concept published
- RUNG 3Exploited in the wild · CISA KEV listed
- RUNG 4Ransomware campaign use known
A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.
What it is stated by the CNA
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.ov receipt
Read the rest of the CNA's description
erride.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.
NVD's analysis a second authority
- weakness
- CWE-502
- affected versions
- apache kafka >= 2.3.0 < 3.9.1
- also scored by
- 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
check it yourself kafka.apache.org receipt
Movement the material steps
This score more than doubled inside 72 hours. Both observations are in the full history below.
Show all 29 observations
29 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt
The full biography
Exploit probability more than doubled between 2025-06-10 and 2025-06-11 (0.00024 → 0.00048) and the record had been public for 1 year, 3 months when this index was last written.
The pattern, elsewhere
This record is one instance of CWE-502, deserialization of untrusted data. The index holds 3288 prior instances of this class, 76 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]
"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1
3288 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.
No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.
Siblings and hubs
Records related to this one
No record cites this identifier and it carries no alias. Its defect family is below.
Its defect family
apache software foundation apache kafka
Of the 2 records in this family, this is the only one whose title names ldaploginmodule.
Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.
Family membership: held values
This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.
Browse the index from here
These are index-wide views, not findings about CVE-2025-27818.
What usually comes next
Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.