cve.bz

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

9.1 criticalEPSS 0.6%

Critical (9.1) in apache software foundation apache kafka. EPSS 0.6% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

9.1 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
EPSS
0.6% (unchanged from 0.6% a week ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
Assigned by
apache (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-111115 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111115?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111115?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111115 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • apache software foundation:apache kafka

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Kafkafrom 2.4.0 through 4.1.2
Apache Software Foundation Apache Kafkafrom 4.2.0 through 4.2.1
Apache Software Foundation Apache Kafkafrom 4.3.0 through 4.3.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
UbuntuPro:18.04:LTSkafkano fix listedUBUNTU-CVE-2026-111115

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important because an unauthenticated remote attacker can trigger severe broker heap exhaustion or prolonged garbage collection stalls without requiring valid credentials or permissions. Because flexible request headers are parsed on network listener threads prior to access control and quota enforcement, any client capable of establishing a TCP connection to an exposed Kafka broker port can trigger the denial of service. While standalone client applications are typically unaffected, deployments hosting Kafka broker services that accept traffic from untrusted networks face immediate service availability risks.

Red Hat's mitigation

Restrict network exposure of Kafka broker listener ports and reduce the maximum permitted request frame size:

1. Restrict broker network access:

Limit connectivity to broker listeners (default port 9092/tcp) to trusted clients and internal subnets using firewall rules:

```

firewall-cmd --permanent --zone=trusted --add-source=192.168.1.0/24

firewall-cmd --reload

```

2. Reduce request size limits:

In the Kafka broker configuration file (such as `server.properties`), reduce the outer request frame limit by lowering `socket.request.max.bytes` to a smaller value appropriate for your workload:

```

socket.request.max.bytes=10485760

```

Caveats:

Modifying `socket.request.max.bytes` requires restarting the Kafka broker service (`systemctl restart ...`), which causes a temporary interruption of service. Lowering this value will cause requests exceeding the threshold to be dropped, potentially affecting legitimate producers or consumers if set below maximum valid message sizes. Restricting network access and lowering the threshold reduces the amplification risk but does not entirely eliminate exposure for connections originating from permitted networks.

ProductPackageStateAdvisory
OpenShift Serverlessopenshift-serverless-1/kn-ekb-dispatcher-rhel9Not affected
OpenShift Serverlessopenshift-serverless-1/kn-ekb-receiver-rhel9Not affected
Red Hat build of Apache Camel 4 for Quarkus 3kafka-clientsAffected
Red Hat build of Apache Camel for Spring Boot 4kafka-clientsAffected
Red Hat build of Apicurio Registry 3kafka-clientsAffected
Red Hat build of Debezium 3kafka-clientsAffected
Red Hat build of Quarkuskafka-clientsAffected
Red Hat Fuse 7kafka-clientsFix deferred
streams for Apache Kafka 3kafka-clientsAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-111115.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON