Apache Kafka: PushTelemetry (KIP-714) metrics payloads are decompressed without a size limit, allowing a broker
Affects kafkaSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.3.1 or 4.2.2 when convenient.
Data as of 17 Nov 2026, 16:49 UTC
Thin evidence
One scorer or none| CISA-ADP | CVSS 3.1 | 6.5 |
|---|
- Patch
- Available – fixed in 4.3.1, 4.2.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade kafka to 4.3.1 or 4.2.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamikafkapkg:bitnami/kafkaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Apache Kafka to version 4.2.2, 4.3.1, or 4.4.0, where the decompression size is properly bounded by telemetry.max.bytes, preventing excessive memory consumption. On affected versions, there is no configuration to fully prevent the amplification; lowering telemetry.max.bytes reduces the worst-case decompressed size proportionally and can serve as a partial mitigation. However, applying the official fix is strongly recommended.
Description
Apache Kafka's PushTelemetry API (KIP-714) decompresses client metrics payloads without limiting the decompressed size, allowing an authenticated client to send a small compressed payload that expands to a very large size in memory. This can exhaust broker heap memory, causing OutOfMemoryError and potentially crashing or degrading broker availability. The vulnerability affects Kafka versions from 3.7.0 up to but not including 4.2.2, and from 4.3.0 up to but not including 4.3.1. Fixed versions 4.2.2, 4.3.1, and 4.4.0 enforce a decompression size limit equal to telemetry.max.bytes (default 1 MB), preventing excessive memory use.