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

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

CVE-2026-111115 · published 21 days ago
Summary

Kafka brokers can be forced to use all their memory when a client sends a specially formed request that lists millions of extra fields. This can cause the broker to pause or stop responding, even before the client is authenticated. Upgrade the broker to the latest release or, as a temporary measure, limit the maximum request size and restrict network access to the broker.

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 tagged-field allocation amplification in flexible protocol request parsing
Apache Kafka's code-generated readers for flexible protocol versions read a tagged-field count declared by the sender and retain a RawTaggedField object for each unknown field. That count was bounded only by the outer request frame size (socket.request.max.bytes); it was not checked against the remaining buffer bytes or capped. Because each entry can be encoded in as little as two bytes (unknown tag 0, size 0), a modest request can declare tens of millions of tagged fields and force one object allocation per declared field. Flexible request headers (header version 2, used by flexible APIs such as ApiVersions v3) are parsed this way, so the amplification applies to the request header itself. Impact: The flexible request header is parsed on the network thread before authorization, request dispatch, and request-time quota accounting. A client can send a request of a few tens of megabytes whose header declares about 20 million tagged fields, forcing roughly that many RawTaggedField allocations and exhausting broker heap or inducing process-wide GC stalls, denying broker service. Because the header is parsed for pre-authentication APIs such as ApiVersions (v3), the allocation can occur before authentication; no Kafka resource ACL or quota is required. 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 bounds-check the tagged-field count for flexible-versioned messages, rejecting a negative count, a count exceeding the remaining buffer bytes, or a count exceeding a fixed maximum (10,000), before any per-field allocation.
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-770Allocation of Resources Without Limits
Timeline
Published28 Oct 2026
Updated19 Nov 2026
First seen28 Oct 2026
Track software like this
Free during beta