Live › vulnerability › CVE-2026-111551
Go to dashboardSeveral Kafka Streams and clients deserializers trust a size or count field in the input and allocate memory for it without checking the bytes actually present. A crafted record or offset metadata can make a consumer or Streams thread throw OutOfMemoryError and crash.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 17:34 UTC. All times on this page are UTC.
Teams running Kafka Streams applications or consumers that use the clients library's ListSerde or ListDeserializer. The Streams paths matter if other principals can write to the application's changelog or repartition topics or commit to its consumer group. The broker itself is not affected, so teams that only run brokers and use no Kafka client code can skip it.
No product ranges from the sources yet.
kafka-topics.sh --version or check the Kafka version in your build file for the clients or Streams library4.2.2, 4.3.2, or 4.4.0Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-111551")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.