CVE-2026-111073

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.

• CWE-400
• CWE-409
• CWE-770

• https://kafka.apache.org/cve-list
• https://www.openwall.com/lists/oss-security/2026/10/28/11

Published

Oct 28, 2026

Last Modified

Nov 5, 2026

Status

Awaiting Analysis

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-111065AIOHTTP is an asynchronous HTTP client/server framework for …6.9
• CVE-2026-111066AIOHTTP is an asynchronous HTTP client/server framework for …8.2
• CVE-2026-111068The DesignSetGo plugin for WordPress is vulnerable to Stored…4.4
• CVE-2026-111069The GeoDirectory – WP Business Directory Plugin and Classifi…6.4
• CVE-2026-11107Inappropriate implementation in Downloads in Google Chrome p…4.3
• CVE-2026-111070The Content Pilot – Autoblogging & Affiliate Marketing Suite…5.4
• CVE-2026-111074In Eclipse OpenJ9 versions prior to 0.63.0, the JITServer co…8.7
• CVE-2026-111075In Eclipse OpenJ9 versions prior to 0.63.0, the JITServer co…8.7
• CVE-2026-111079A flaw was found in Goose. When the terminal integration fea…7.4
• CVE-2026-11108Inappropriate implementation in NFC in Google Chrome on Andr…8.8
• CVE-2026-111085Rejected reason: This CVE ID has been rejected or withdrawn …
• CVE-2026-111088A Stored Cross-Site Scripting vulnerability exists in the SN…6.5