Skip to content
VulniPulse
Sign in
Highest advisory severityMedium 2 vendors · 2 advisories

CVE-2026-111073

Denial of Service via unbounded telemetry payload decompression

CVE-2026-111073: Denial of Service via unbounded telemetry payload decompression. Not in the CISA KEV catalog. Medium advisory severity (CVSS 6.5, Red Hat).

Compare the source-linked records below. Ratings and product/version details belong to each advisory; they are not a single CVE-wide score or proof that every listed product is affected. How VulniPulse collects and checks evidence.

NVD detail CVE.org

Get an email when Apache publishes the next one.

VulniPulse checks Apache's security advisories around the clock and emails you new ones with the severity, the fixed version and the vendor's link. First month free, then US$15/month; we email you before the first charge.

Start your free month

CVE-2026-111073 key facts

CISA KEV
Not listed (catalog checked )
Highest advisory severity
Medium
CVSS base score
6.5 (Red Hat)
Fixed releases
  • Apache: 4.2.2, 4.3.1, 4.4.0
  • Red Hat: 4.2.2, 4.3.1, 4.4.0
Vendor advisories
2 from Apache, Red Hat
VulniPulse record
Published · Updated

Scores, vectors, weaknesses and fixed releases are quoted from vendor advisories that cover only CVE-2026-111073; bulletin-wide values are not repeated here.

Is CVE-2026-111073 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-111073 is not in the CISA KEV catalog (checked ) and no tracked advisory for it reports exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-111073?

Upgrade to a fixed release named by the vendor:

  • Apache: 4.2.2, 4.3.1, 4.4.0
  • Red Hat: 4.2.2, 4.3.1, 4.4.0
  • ClientTelemetryUtils.decompress() then decompresses the payload with no limit on the decompressed output size, growing a heap buffer until the compressed input is exhausted. (Apache)
  • Mitigation: Upgrade to Apache Kafka 4.2.2, 4.3.1, or 4.4.0. (Apache)
  • 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. (Red Hat)

Vendor advisory comparison

Apache

1 advisory
  • Advisory severityUnrated

    Advisory [CVE-2026-111073] Apache Kafka: 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

    CVE-2026-111073Source published Source updated

    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…

    Affected products in this advisory
    • Apache Kafka
    Source-reported affected versions
    • Apache Kafka 3.7.0 through 4.1.2
    • Apache Kafka 4.2.0 through 4.2.1
    • Apache Kafka 4.3.0
    Source-reported fixed versions
    • 4.2.2
    • 4.3.1
    • 4.4.0
    Mitigation guidance
    • ClientTelemetryUtils.decompress() then decompresses the payload with no limit on the decompressed output size, growing a heap buffer until the compressed input is exhausted.
    • Mitigation: Upgrade to Apache Kafka 4.2.2, 4.3.1, or 4.4.0.
    • 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.
    Full advisory and evidenceOpen source bulletin

Red Hat

1 advisory
  • Advisory severityMedium6.5

    Medium [CVE-2026-111073] Denial of Service via unbounded telemetry payload decompression

    CVE-2026-111073Source published Source updated

    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…

    Affected products in this advisory
    • OpenShift Serverless
    • Red Hat build of Apache Camel 4 for Quarkus 3
    • Red Hat build of Apache Camel for Spring Boot 4
    • Red Hat build of Apicurio Registry 3

    4 more entries in the full advisory.

    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    • 4.2.2
    • 4.3.1
    • 4.4.0
    Mitigation guidance
    • 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.
    Full advisory and evidenceOpen source bulletin

More Apache advisories

All Apache advisories

Follow CVE-2026-111073 in the free weekly digest

Every Monday: whether it was added to CISA KEV, reported exploited, got a fix or changed severity, plus the week's critical and high advisories.

Free, no account. Confirm by email; unsubscribe in one click. Choose vendors and severity

Browse the latest tracked CVEs or the CVEs listed in CISA KEV.

Android app · Google Play

Get alerts for new CVEs on your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features