cve.bz

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

7.5 highEPSS 0.5%

High (7.5) in apache software foundation apache kafka. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
Several Kafka deserialization paths read a size or count field from input data and use it directly to allocate an array, collection, or byte buffer, with no check against the bytes actually available. A small crafted input can therefore declare a very large size and force a multi-gigabyte allocation. The affected paths are, in Kafka Streams, ProcessorRecordContext (header count), ChangedDeserializer (varint value length), CombinedKeySchema (foreign-key length, which could also produce a negative size), ProcessorMetadata (key length), and AssignmentInfo group-assignment decoding; and, in the clients library, ListDeserializer (used by ListSerde). Impact: An attacker can trigger the oversized allocation and raise an OutOfMemoryError that crashes the affected consumer or Kafka Streams thread; the broker and the rest of the cluster are unaffected. The reachable surface depends on the path: writing a crafted record to a Streams application's internal changelog or repartition topics, or committing crafted offset metadata to its consumer group (Streams internal paths); writing a crafted record to any topic that a consumer reads with ListSerde (ListDeserializer); or, as a member of a Streams consumer group, returning crafted assignment data when elected leader (AssignmentInfo). Because a crafted record remains in its topic, the error can recur on restart. The record size limit (max.message.bytes) does not help, because the allocation is driven by a size field rather than by the input's length. Mitigation: Upgrade to Apache Kafka 4.2.2, 4.3.2, or 4.4.0. Where authorization is enabled, restrict write access to each application's internal topics and consumer group to its own principal, and restrict who can produce to topics that are consumed with ListSerde. Resolution: From Apache Kafka 4.2.2, 4.3.2, and 4.4.0: these deserialization paths validate the declared size against the remaining input before allocating and reject input that fails the check.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 43rd 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-20 Improper Input Validation
CWE-400 Uncontrolled Resource Consumption
CWE-789 Memory Allocation with Excessive Size Value
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

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

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 an Important severity because remote actors capable of publishing messages to topics processed by Kafka Streams or clients using specific deserializers can repeatedly trigger out-of-memory crashes on consumer applications. While the Kafka broker infrastructure itself remains operational, client applications and stream workers consuming from untrusted sources face complete denial of service that persists across application restarts. The flaw predominantly affects environments where message production to internal stream topics or consumer-group metadata is not strictly restricted by authentication and authorization boundaries.

Red Hat's mitigation

Upgrade to Apache Kafka 4.2.2, 4.3.2, or 4.4.0. The flaw is in the kafka-streams and kafka-clients libraries; the broker is not affected. The max.message.bytes record size limit does not prevent this, because the allocation is driven by a size field read from the record rather than by the record's actual length. Where authorization is enabled, restrict write access to each Streams application's internal topics and consumer group to the application's own principal, and restrict who can produce to topics that are consumed with ListSerde. A crafted record remains in its topic, so the failure recurs after restart until the offending records are removed or the application is upgraded.

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 build of Quarkuskafka-streamsAffected
Red Hat Fuse 7kafka-clientsFix deferred
Red Hat Fuse 7kafka-streamsFix deferred
streams for Apache Kafka 3kafka-clientsAffected
streams for Apache Kafka 3kafka-streamsAffected

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

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-20 (51).

References

Check your stackJSON