Apache Kafka: Broker OutOfMemoryError via tagged-field allocation amplification in flexible protocol request parsing
Affects kafkaSource GCVE Database
Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.3.2 or 4.2.2 as a priority.
Data as of 17 Nov 2026, 16:49 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 9.1 |
|---|
- Patch
- Available – fixed in 4.3.2, 4.2.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade kafka to 4.3.2 or 4.2.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamikafkapkg:bitnami/kafkaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Apache Kafka to version 4.2.2, 4.3.2, or 4.4.0 where the vulnerability is fixed. Until upgrading, reduce the socket.request.max.bytes configuration to limit maximum request size and restrict network access to broker listeners to reduce exposure. These mitigations reduce but do not eliminate the risk.
Description
Apache Kafka versions prior to 4.2.2 and between 4.3.0 and 4.3.2 have a vulnerability in the parsing of flexible protocol request headers. An attacker can send a request with a large declared count of tagged fields, causing excessive memory allocation and potentially exhausting broker heap memory or causing process-wide garbage collection stalls. This can lead to denial of service on the broker. The issue occurs before authentication and authorization, so no ACL or quota is required to exploit it. Fixed in versions 4.2.2, 4.3.2, and 4.4.0.