Technical impact
A client can send Kafka requests whose flexible protocol headers declare an enormous number of tagged fields, forcing the broker to allocate a RawTaggedField object per field before any authentication or authorization checks. This lack of bounds checking (CWE‑770) can exhaust the broker’s heap or trigger prolonged garbage‑collection pauses, causing the broker to become unresponsive. The vulnerability is an example of uncontrolled resource consumption and could compromise availability even when the client is unauthenticated.
Affected Systems
The problem exists in all Apache Kafka releases that do not include the patch from Apache Software Foundation version 4.2.2, 4.3.2, or 4.4.0. The impact is limited to brokers that accept flexible protocol requests, particularly pre‑authentication APIs like ApiVersions (v3).
Risk and Exploitability
With a CVSS score of 9.1, the vulnerability is considered a high severity. The EPSS score of < 1% indicates a low probability of exploitation, yet because no authentication or ACLs are required, any client can trigger the DoS by sending a flexible protocol header that declares millions of tagged fields, forcing massive allocations and exhausting system resources. The risk is that the broker service becomes unavailable, with no impact on data integrity or confidentiality, and the vulnerability is currently not listed in the CISA KEV catalog.