CVE-2026-111073

NONE

Published: 2026-10-28

Modified: 2026-10-29

Enriched via mock

Tenable Plugin

Checking the public Tenable catalog…

AI Threat Summary

CVE-2026-111073 is a moderate vulnerability affecting the target software. Threat hunters should monitor for exploit attempts and apply vendor patches immediately.

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.

Attack Chain

Reconnaissance

Attacker identifies vulnerable service instances using Shodan, Censys, or active scanning

Initial Access

Attacker crafts malicious payload exploiting CVE-2026-111073 to achieve remote code execution

Execution

Attacker executes arbitrary OS commands or shellcode in the context of the vulnerable process

Persistence

Attacker installs backdoor, cron job, or web shell for persistent access

Lateral Movement

Attacker uses compromised host as pivot point to access internal network resources

MITRE ATT&CK Techniques

T1190 Exploit Public-Facing Application

Initial Access

Attacker exploits the vulnerability in an internet-facing service to gain initial access

T1059 Command and Scripting Interpreter

Execution

Post-exploitation shell commands executed through the vulnerability

T1105 Ingress Tool Transfer

Command and Control

Attacker downloads malware or tools after gaining code execution

Indicators of Compromise

Type	Value	Description
user_agent	`Mozilla/5.0 (compatible; exploit/1.0)`	Generic exploit scanner user agent pattern
url	`/api/vuln-endpoint?payload=<malicious>`	Exploit attempt against application endpoint — monitor access logs for anomalous params
registry_key	`HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run\backdoor`	Persistence mechanism after successful RCE

Remediation

1. Apply vendor-supplied security patches immediately. 2. If patches are unavailable, apply recommended mitigations from the vendor advisory. 3. Enable WAF rules or IDS signatures to detect exploitation attempts. 4. Monitor logs for indicators of compromise listed above. 5. Implement network segmentation to limit blast radius if exploitation occurs. 6. Subscribe to vendor security advisories for this product.

Quick Facts

CVE ID	CVE-2026-111073
CVSS Score	N/A
Published	2026-10-28
Exploited	No
CISA KEV	No
PoC	Not public

References

External Resources

NVD Entry BleepingComputer The Hacker News