CVE-2026-111073VulnerabilityPublished 28 Oct 2026

The broker-side PushTelemetry API (KIP-714) validates only the compressed size of a client's metrics payload against

Source GCVE Database

Authoritative record:CVE-2026-111073· High

Not known to be exploited.

Data as of 28 Oct 2026, 19:57 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-r6fp-x62f-pxfv

What to do

Affected software

Product	Affected	Fixed in
Apache Kafkaorg.apache.kafka:kafka	Affected >=3.7.0 <=4.1.2 >=4.2.0 <=4.2.1 =4.3.0	Fixed in–
MavenApache Software Foundation/org.apache.kafka:kafka`pkg:maven/Apache Software Foundation/org.apache.kafka:kafka`Other threats	Affected >=3.7.0 <=4.1.2 >=4.2.0 <=4.2.1 =4.3.0	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 process enforces a maximum decompressed size equal to telemetry.max.bytes, preventing excessive memory consumption. On affected versions, no configuration fully prevents this amplification; lowering telemetry.max.bytes reduces the worst-case decompressed size proportionally and serves only as a partial mitigation.

Description

The broker-side PushTelemetry API in Apache Kafka versions prior to 4.2.2, 4.3.1, and 4.4.0 validates only the compressed size of telemetry payloads before decompressing them. This allows an authenticated client to send a small compressed payload that decompresses to a very large size, consuming excessive broker heap memory. This can lead to OutOfMemoryError conditions, degrading or crashing the broker and potentially affecting cluster availability. The vulnerability is mitigated in Apache Kafka 4.2.2, 4.3.1, and 4.4.0 by enforcing a maximum decompressed size equal to telemetry.max.bytes, aborting decompression if exceeded.

Impact

An authenticated client can cause a denial of service by sending a small compressed telemetry payload that decompresses to a very large size, consuming excessive heap memory on the broker. This can lead to OutOfMemoryError, degrading or crashing the broker and potentially impacting the availability of the Kafka cluster. Since PushTelemetry is accessible to any authenticated client and not restricted by ACLs, the risk is significant for authenticated users.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Oct 2026, 19:57 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats