Improper Handling of Highly Compressed Data (Data Amplification) Affecting org.apache.kafka:kafka-clients package, versions [3.7.0,4.2.2)[4.3.0,4.3.1)


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.43% (38th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-JAVA-ORGAPACHEKAFKA-22150240
  • published3 Nov 2026
  • disclosed28 Oct 2026
  • creditDawit Jeong

Introduced: 28 Oct 2026

NewCVE-2026-111073  (opens in a new tab)
CWE-409  (opens in a new tab)

How to fix?

Upgrade org.apache.kafka:kafka-clients to version 4.2.2, 4.3.1 or higher.

Overview

org.apache.kafka:kafka-clients is a streaming platform that can publish and subscribe to streams of records, store streams of records in a fault-tolerant durable way, and process streams of records as they occur.

Affected versions of this package are vulnerable to Improper Handling of Highly Compressed Data (Data Amplification) via the decompress function in ClientTelemetryUtils during broker-side PushTelemetry processing. An authenticated client can exhaust broker heap by sending a small, highly compressible metrics payload that passes the compressed-size limit but expands without a decompressed-size limit, causing an OutOfMemoryError that degrades or crashes the broker. PushTelemetry is not gated by an ACL, and repeated or concurrent requests can affect cluster availability.

Notes

  • The compressed input is capped by telemetry.max.bytes (default 1 MB); lowering it reduces the worst-case expansion proportionally, but does not prevent the amplification.

Workarounds

  • Lower telemetry.max.bytes on affected brokers to reduce the worst-case decompressed payload size and resulting heap consumption; this is only a partial mitigation.

CVSS Base Scores

version 4.0
version 3.1