# 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 (de


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-r6fp-x62f-pxfv, UBUNTU-CVE-2026-111073

## What is CVE-2026-111073?

CVE-2026-111073 is a vulnerability in Apache Kafka, published on 28 Oct 2026. 

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification)), CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-111073?


## How do I fix CVE-2026-111073?

No fix has been published for CVE-2026-111073 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111073 being exploited?

There is no known exploitation of CVE-2026-111073 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111073 and fix it if it is affected.

What it is: CVE-2026-111073 is a vulnerability in Apache Kafka, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111073 in the wild and no public exploit code.

Affected product: Apache Kafka. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111073/ (Markdown: https://insights.sbomify.com/CVE-2026-111073/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111073
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111073
- OSV: https://osv.dev/vulnerability/CVE-2026-111073

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111073/
Summaries are generated and may contain mistakes; the official description above is the record.