Skip to main content
CVE-2026-111108VulnerabilityPublished

Apache Kafka: Broker OutOfMemoryError via array allocation amplification in code-generated protocol readers

Affects kafkaSource GCVE Database

0
Compare
Authoritative record:CVE-2026-111108· Critical 9.1

Not known to be exploited · CVSS 9.1 Critical : upgrade to 4.3.2 or 4.2.2 as a priority.

Data as of 17 Nov 2026, 16:49 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.19.1
Patch
Available – fixed in 4.3.2, 4.2.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 16 Nov 2026.

What to do

Upgrade kafka to 4.3.2 or 4.2.2.

Affected software

ProductAffectedFixed in
Bitnamikafkapkg:bitnami/kafkaOther threatsAffected
  • >=3.3.0 <4.2.2
  • >=4.3.0 <4.3.2
Fixed in
  • 4.2.2
  • 4.3.2

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 versions 4.2.2, 4.3.2, or 4.4.0 where the vulnerability is fixed. Until upgrading, reduce exposure by lowering the socket.request.max.bytes configuration and restricting network access to broker listeners. These mitigations reduce but do not eliminate the risk. The vendor advisory confirms that the fix caps array pre-allocation and rejects overly large array lengths.

Description

Apache Kafka contains a vulnerability in its code-generated protocol readers where an attacker can cause the broker to allocate excessive heap memory by declaring an array length much larger than the actual request buffer size. This leads to an OutOfMemoryError and broker crash. The issue affects all Kafka API types with array fields and occurs before authorization checks, allowing unauthenticated attackers on unauthenticated listeners to exploit it. The vulnerability is fixed in Apache Kafka versions 4.2.2, 4.3.2, and 4.4.0.

References

Community reviews

Loading reviews…