Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.1

CVE-2026-111108: Apache Kafka can run out of memory from crafted requests

CVE-2026-111108 · published 21 days ago
Summary

Kafka brokers that accept unauthenticated network traffic can be forced to allocate far more memory than the size of the incoming data. By sending requests that claim an extremely large number of items, an attacker can cause the broker to exhaust its heap and crash. Update to the latest Kafka release or limit the size of incoming requests and restrict network access to the broker listeners to reduce the risk.

What to do
  • Update kafka to version 4.3.2.
Affected software
Ecosystem VendorProductAffected versions
– apache software foundation apache kafka <= 4.1.2
Ubuntu:Pro:18.04:LTS canonical kafka All versions
Bitnami – kafka >= 4.3.0, < 4.3.2
Fix: upgrade to 4.3.2
Original advisory text
Apache Kafka: Broker OutOfMemoryError via array allocation amplification in code-generated protocol readers
Apache Kafka's code-generated protocol readers pre-size an array's collection from the element count declared by the sender. That count is checked only against the bytes remaining in the request buffer, which assumes about one byte per element; because most elements need several bytes, a request can declare far more elements than the buffer holds and still pass. For a keyed array the reader then allocates an ImplicitLinkedHashCollection of capacity (2 * count +1), so a request of a few tens of megabytes can force a heap allocation several times larger before any element is read. The pattern is emitted into every generated reader, so it affects all Kafka API types with an array field. Impact: Request parsing happens before any authorization check. On a listener that does not require authentication (for example PLAINTEXT), an unauthenticated attacker can send a few concurrent requests that each declare a very large= array length and allocate many times their wire size in broker heap, crashing the broker with an OutOfMemoryError. The reporter demonstrated three concurrent ~90 MB ProduceRequest (v3) connections exhausting a 1 GB heap (~8x amplification). On listeners that require authentication, the attacker needs valid credentials but no specific ACL, since parsing precedes authorization.. Mitigation: Upgrade to Apache Kafka 4.2.2, 4.3.2, or 4.4.0. Until then, lowering socket.request.max.bytes and restricting network access to broker listeners reduces, but does not remove, exposure. Resolution: From Apache Kafka 4.2.2, 4.3.2, and 4.4.0: generated readers cap the initial array pre-allocation at MessageUtil.MAX_PREALLOCATED_ARRAY_CAPACITY (1000) and grow it on demand, and reject a declared array length above MessageUtil.MAX_ARRAY_LENGTH (1,000,000).
Fix within
Internet-facing 14 days
Internal 60 days
  • Not known to be exploited
  • Can be exploited automatically
  • Gives an attacker partial control
Severity
9.1 Critical
Exploitation
<1% chance of attack within 30 days
Type
CWE-400Uncontrolled Resource Consumption
CWE-770Allocation of Resources Without Limits
CWE-789Memory Allocation with Excessive Size Value
Timeline
Published28 Oct 2026
Updated19 Nov 2026
First seen28 Oct 2026
Track software like this
Free during beta