CVE-2026-111073: Apache Kafka: PushTelemetry (KIP-714) metrics payloads are decompressed without a size limit, allowing a broker out-of-memory denial of service
The broker-side PushTelemetry API (KIP-714) validates only the compressed size of a client's metrics payload against telemetry.max.bytes (default 1 MB) before decompressing it. ClientTelemetryUtils.decompress() then decompresses the payload with no limit on the decompressed output size, growing a heap buffer until the compressed input is exhausted. A small, highly compressible payload (for example gzip-compressed zeros) can therefore expand to hundreds of megabytes of broker heap.
Impact:
An authenticated client can send a PushTelemetry request with a small compressed payload that decompresses to a very large size, consuming broker heap out of proportion to the request size. Repeated or concurrent requests can exhaust the broker heap and cause an OutOfMemoryError, degrading or crashing the broker; a client that targets multiple brokers can affect cluster availability. PushTelemetry is available to any authenticated client and is not gated by an ACL.
Mitigation:
Upgrade to Apache Kafka 4.2.2, 4.3.1, or 4.4.0. On affected versions there is no configuration that fully prevents the amplification, because telemetry.max.bytes bounds only the compressed size; lowering telemetry.max.bytes reduces the worst-case decompressed size proportionally and is a partial mitigation.
Resolution:
- From Apache Kafka 4.2.2, 4.3.1, and 4.4.0: ClientTelemetryUtils.decompress() enforces a maximum decompressed size equal to telemetry.max.bytes (default 1 MB). Decompression reads in bounded chunks and aborts with a TelemetryTooLargeException once the decompressed total exceeds the limit, so an over-large or highly compressible payload is rejected instead of being fully expanded in heap. The decompressed size is therefore bounded by default.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
bitnami/kafkato a version that resolves this vulnerability.Fixed in 4.2.2 - Upgrade
Upgrade
bitnami/kafkato a version that resolves this vulnerability.Fixed in 4.3.1 - Upgrade
Upgrade
Apache Kafkato a version that resolves this vulnerability.Fixed in 4.2.2 - Upgrade
Upgrade
Apache Kafkato a version that resolves this vulnerability.Fixed in 4.3.1 - Upgrade
Upgrade
Apache Kafkato a version that resolves this vulnerability.Fixed in 4.4.0 - Configuration
Lower telemetry.max.bytes as a partial mitigation; this reduces the worst-case decompressed size proportionally but does not fully prevent amplification on affected versions.
Apache Kafka broker telemetry.max.bytes = lower than the current value
Event History
Frequently Asked Questions
Which deployments are realistically exposed to this denial of service?
Any affected broker that accepts authenticated client connections is exposed. PushTelemetry is available to any authenticated client and is not gated by an ACL, so access does not require a specific telemetry-related permission.
What does an attacker need to do to trigger the issue?
An authenticated client must send a PushTelemetry request containing a small compressed metrics payload that expands to a very large amount of data when decompressed. Repeated or concurrent requests can consume enough heap to degrade or crash a broker, and targeting multiple brokers can affect cluster availability.
Does the default telemetry.max.bytes setting prevent exploitation?
No. Its default value is 1 MB, but it validates only compressed payload size before decompression; it does not limit the decompressed output. Lowering this setting does not fully prevent the compression amplification.
What should teams do if they cannot patch immediately?
The provided mitigation states that no configuration on affected versions fully prevents the issue. Upgrade to Apache Kafka 4.2.2, 4.3.1, or 4.4.0.