cve.bz

CVE-2026-111108 apache software foundation apache kafka: Uncontrolled Resource Consumption

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 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).

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; 49th 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.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-770 Allocation of Resources Without Limits or Throttling
CWE-789 Memory Allocation with Excessive Size Value
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-111108 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111108?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111108?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-111108 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 3.3.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-111108

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 flaw is in Apache Kafka broker request parsing: generated protocol readers can pre-allocate large heap collections from an attacker-controlled array length before authorization, enabling out-of-memory denial of service. Red Hat rates it Important for deployments that expose Kafka broker listeners.

Most Red Hat offerings listed against kafka-clients are not affected because they do not run an Apache Kafka broker that accepts Kafka API requests from clients. Quarkus, Camel, Fuse, Debezium, Service Registry, and related cloud-service images use kafka-clients only as producers or consumers against an external cluster. OpenShift Serverless kn-ekb dispatcher/receiver components are a Knative Eventing Kafka data plane (HTTP plus kafka-clients) and are not Kafka brokers, so they are not exposed to this request-parse path. The Red Hat product that remains affected is AMQ Streams, which ships the Kafka broker and falls within the upstream affected version range.

Red Hat's mitigation

Red Hat is not aware of any available mitigation for this issue. Customers are advised to apply the relevant security updates as they become available.

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-clientsNot affected
Red Hat build of Apache Camel for Spring Boot 4kafka-clientsNot affected
Red Hat build of Apicurio Registry 3kafka-clientsNot affected
Red Hat build of Debezium 3kafka-clientsNot affected
Red Hat build of Quarkuskafka-clientsNot affected
Red Hat Fuse 7kafka-clientsNot affected
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-111108.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

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