CVE-2026-111115

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.

• https://kafka.apache.org/cve-list
• https://www.openwall.com/lists/oss-security/2026/10/28/12

Published

Oct 28, 2026

Last Modified

Oct 29, 2026

Status

Awaiting Analysis

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-111108Apache Kafka's code-generated protocol readers pre-size an a…
• CVE-2026-111109The Webmention plugin for WordPress is vulnerable to Stored …6.1
• CVE-2026-11111Out of bounds read in ANGLE in Google Chrome prior to 149.0.…8.1
• CVE-2026-111110The Payment forms, Buy now buttons, and Invoicing System | G…7.2
• CVE-2026-111111The Prime Slider – Hero Slider, Carousel, WooCommerce & Post…7.2
• CVE-2026-111114The Nexter Extension – Security, Performance, Code Snippets …7.5
• CVE-2026-11112Insufficient validation of untrusted input in Chromoting in …9.6
• CVE-2026-111120The VikRentCar Car Rental Management System plugin for WordP…8.8
• CVE-2026-111122The SiteOrigin CSS plugin for WordPress is vulnerable to Sto…7.2
• CVE-2026-111123FluidSynth through 2.6.1 contains an out-of-bounds write vul…6.1
• CVE-2026-111124CFITSIO through 4.7.0 contains a heap-based out-of-bounds re…7.1
• CVE-2026-111125CFITSIO through 4.7.0 contains a heap-based out-of-bounds re…7.1