Skip to main content
CVE-2026-111551VulnerabilityPublished

Apache Kafka: Denial of service

Affects kafkaSource GCVE Database

0
Compare
Authoritative record:CVE-2026-111551· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 4.3.2 or 4.2.2 soon.

Data as of 17 Nov 2026, 16:49 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.17.5
Patch
Available – fixed in 4.3.2, 4.2.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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
  • >=4.2.0 <4.2.2
  • >=4.3.0 <4.3.2
  • >=0.10.0 <=4.1.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 to Apache Kafka versions 4.2.2, 4.3.2, or 4.4.0 where the vulnerability is fixed by validating declared sizes before allocation. Additionally, enable authorization and restrict write access to each application's internal topics and consumer groups to their own principals. Restrict who can produce to topics consumed with ListSerde to reduce exposure.

Description

Apache Kafka contains a vulnerability in several deserialization paths where unbounded memory allocation can be triggered by crafted input declaring large sizes. This can cause an OutOfMemoryError that crashes Kafka Streams or consumer threads. The issue affects Kafka versions prior to 4.2.2, 4.3.2, and 4.4.0. The broker and cluster remain unaffected. The vulnerability is mitigated by upgrading to fixed versions and restricting write access to internal topics and consumer groups.

References

Community reviews

Loading reviews…