CVE-2026-111551

Apache Kafka: Denial of service in Kafka Streams and client deserializers via unbounded memory allocation

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

Analysis

AI-generated

Technical impact

Multiple Kafka deserialization mechanisms read a size or count field from inbound data and allocate a data structure of that exact size without verifying that enough bytes remain. An attacker can send a record that declares a very large, possibly negative, size, causing the JVM to attempt a multi‑gigabyte allocation. The resulting OutOfMemoryError crashes the consumer or Streams processing thread, but the broker and other cluster nodes continue normally. The attacker’s payload can persist on the topic, leading to repeated crashes whenever the topic is read again.

Affected Systems

Apache Kafka platforms are affected; the exact set of vulnerable versions is not listed, but the fix is included in Kafka 4.2.2, 4.3.2, and 4.4.0. Vulnerable deserializers include ProcessorRecordContext in Kafka Streams, ChangedDeserializer, CombinedKeySchema, ProcessorMetadata, AssignmentInfo, and ListDeserializer in the client library.

Risk and Exploitability

The EPSS score of 0.00222 (≈0.22%) indicates a very low but non‑zero exploitation probability, and the vulnerability is not listed in the CISA KEV catalog, suggesting no publicly documented exploits. With a CVSS score of 7.5, the vulnerability is considered high severity, and the risk remains high if the attacker can produce faulty records to an internal changelog, repartition topic, or any topic used with ListSerde, as the error manifests on any read. Attackers require access to produce to the victim’s Kafka topics or to be a member of a Streams consumer group to inject assignment data. Even with limited write rights, crafted metadata can trigger an OOM in a coordinator if proper permissions are not enforced. In environments where authorization is turned off, the attack surface is broad; with authorization enabled, the surface can be reduced but remains significant if principals are able to write to internal partitions or produce to ListSerde-consumed topics.

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, which add bounds checks before allocation.
  • When authorization is enabled, restrict write permissions on the Streams internal changelog, repartition, and other internal topics to the application’s own principal.
  • Restrict publication to any topic that is consumed with ListSerde to principals that must not generate malformed records, and ensure consumers of those topics are also configured to enforce limits.

Generated by OpenCVE AI on October 30, 2026 at 14:00 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
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
Description 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.
Title Apache Kafka: Denial of service in Kafka Streams and client deserializers via unbounded memory allocation
Weaknesses CWE-20
CWE-400
CWE-789
References
Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling

  • CWE-789

    Memory Allocation with Excessive Size Value

Sources

Status
PUBLISHED
Assigner
apache
Published
Updated
Nov 5, 2026, 5:13 PM
Reserved
Oct 16, 2026, 11:01 AM
Status
Awaiting Analysis
Published
Oct 28, 2026, 5:17 PM
Modified
Nov 5, 2026, 5:17 PM
Severity
Important
Public date
Oct 28, 2026, 4:45 PM