CVE-2026-111115

Apache Kafka: Broker OutOfMemoryError via tagged-field allocation amplification in flexible protocol request parsing

Published Oct 28, 2026 CVSS 3.1 · 9.1 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

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.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apache Kafka to version 4.2.2, 4.3.2, or 4.4.0.
  • Configure the broker’s socket.request.max.bytes setting to a lower value to limit request size.
  • Restrict network access to broker listeners so that only trusted hosts can connect.

Generated by OpenCVE AI on November 5, 2026 at 21:28 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H'}

Type Values Removed Values Added
Weaknesses CWE-400
Type Values Removed Values Added
Weaknesses CWE-770
References
Metrics threat_severity

None

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Important

Type Values Removed Values Added
First Time appeared Apache
Apache kafka
Vendors & Products Apache
Apache kafka
Type Values Removed Values Added
Weaknesses CWE-400
Type Values Removed Values Added
Description 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.
Title Apache Kafka: Broker OutOfMemoryError via tagged-field allocation amplification in flexible protocol request parsing
References
Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 11, 2026, 11:31 AM
Reserved
Oct 15, 2026, 4:27 PM
Status
Awaiting Analysis
Published
Oct 28, 2026, 5:17 PM
Modified
Nov 11, 2026, 12:18 PM
Severity
Important
Public date
Oct 28, 2026, 4:44 PM