cve.bz

CVE-2026-111073 apache software foundation apache kafka: Uncontrolled Resource Consumption

6.5 mediumEPSS 0.4%

Medium (6.5) in apache software foundation apache kafka. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-11-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-400 Uncontrolled Resource Consumption
CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
CWE-770 Allocation of Resources Without Limits or Throttling
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-111073 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111073?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111073?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111073 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • apache software foundation:apache kafka

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Kafkafrom 3.7.0 through 4.1.2
Apache Software Foundation Apache Kafkafrom 4.2.0 through 4.2.1
Apache Software Foundation Apache Kafka4.3.0

Linux distributions

DistributionReleasePackageFixed inAdvisory
UbuntuPro:18.04:LTSkafkano fix listedUBUNTU-CVE-2026-111073

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate impact because successful exploitation requires an authenticated client and only causes a denial of service, without compromising system confidentiality or data integrity. In typical Red Hat deployments containing Apache Kafka brokers, telemetry intake is exposed to all authenticated connections without access control list enforcement. A malicious or compromised authenticated user can transmit highly compressible metrics data that expands upon decompression, exhausting broker heap memory and degrading cluster stability.

Red Hat's mitigation

Lower the `telemetry.max.bytes` configuration parameter on Kafka brokers to limit the size of compressed telemetry payloads processed into memory.

In the Kafka broker configuration file (`server.properties`), set a reduced value for the telemetry payload limit (for example, 100 KB):

telemetry.max.bytes=102400

Caveats:

This provides a partial mitigation. Decreasing this parameter reduces the worst-case decompressed heap allocation proportionally, but does not completely eliminate memory amplification. In addition, legitimate clients transmitting valid telemetry metrics exceeding this configured limit will be rejected.

Warning: Modifying the broker configuration requires restarting the Kafka broker service, which can cause temporary service interruption if not performed in a rolling restart fashion across the cluster.

ProductPackageStateAdvisory
OpenShift Serverlessopenshift-serverless-1/kn-ekb-dispatcher-rhel9Fix deferred
OpenShift Serverlessopenshift-serverless-1/kn-ekb-receiver-rhel9Fix deferred
Red Hat build of Apache Camel 4 for Quarkus 3kafka-clientsFix deferred
Red Hat build of Apache Camel for Spring Boot 4kafka-clientsFix deferred
Red Hat build of Apicurio Registry 3kafka-clientsFix deferred
Red Hat build of Debezium 3kafka-clientsFix deferred
Red Hat build of Quarkuskafka-clientsFix deferred
Red Hat Fuse 7kafka-clientsOut of support scope
streams for Apache Kafka 3kafka-clientsFix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-111073.

Attack patterns (CAPEC)

  • CAPEC-147 XML Ping of the Death Likelihood: Low · Severity: Medium
  • CAPEC-227 Sustained Client Engagement
  • CAPEC-492 Regular Expression Exponential Blowup

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

References

Check your stackJSON