CVE-2026-114349VulnerabilityPublished 28 Oct 2026

When a broker decodes a compressed record batch, the per-record decoder reads a declared body size from the

Source GCVE Database

Authoritative record:CVE-2026-114349· High

Not known to be exploited.

Data as of 28 Oct 2026, 20:00 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-6rr8-5qq5-gq73

What to do

Affected software

Product	Affected	Fixed in
Apache Kafkaorg.apache.kafka:kafka	Affected >=0.11.0.0 <=4.1.2 >=4.2.0 <=4.2.1 >=4.3.0 <=4.3.1	Fixed in–
MavenApache Software Foundation/org.apache.kafka:kafka`pkg:maven/Apache Software Foundation/org.apache.kafka:kafka`Other threats	Affected >=0.11.0.0 <=4.1.2 >=4.2.0 <=4.2.1 >=4.3.0 <=4.3.1	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.2, or 4.4.0, which enforce validation of the declared decompressed record size against the max.decompressed.message.bytes configuration. Additionally, set max.decompressed.message.bytes at the broker and/or topic level to a bounded value appropriate for your workload, as the default is effectively unlimited and does not mitigate the issue alone. Until upgrade and configuration are applied, restrict Write access to trusted producers. Quotas and max.message.bytes settings do not mitigate this vulnerability.

Description

A vulnerability in Apache Kafka allows an authenticated user with Write permission on a topic to cause an OutOfMemoryError by sending a compressed record batch with a maliciously declared decompressed body size. This can crash broker request-handler threads and consumer processes, leading to denial of service. On brokers configured with -XX:+ExitOnOutOfMemoryError, the JVM can terminate. Additionally, the log cleaner thread can be terminated permanently on compacted topics, halting log compaction and affecting broker availability until manual intervention. No data disclosure or alteration occurs.

Impact

An authenticated principal with Write permission can cause denial of service by crashing broker request-handler threads and consumers via OutOfMemoryError. Brokers started with -XX:+ExitOnOutOfMemoryError may terminate the JVM on a single crafted request. The log cleaner thread can be permanently terminated on compacted topics, stopping log compaction and affecting broker availability and internal topic maintenance until the offending record is removed. No data confidentiality or integrity is affected.

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, 20:00 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats