Allocation of Resources Without Limits or Throttling Affecting kafka-4.3 package, versions <4.3.1-r12


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.37% (29th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-CHAINGUARDLATEST-KAFKA43-20652895
  • published9 Oct 2026
  • disclosed6 Oct 2026

Introduced: 6 Oct 2026

NewCVE-2026-106450  (opens in a new tab)
CWE-770  (opens in a new tab)

How to fix?

Upgrade Chainguard kafka-4.3 to version 4.3.1-r12 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream kafka-4.3 package and not the kafka-4.3 package as distributed by Chainguard. See How to fix? for Chainguard relevant fixed versions and status.

yawkat LZ4 Java provides LZ4 compression for Java. Prior to 1.11.4, net.jpountz.lz4.LZ4FrameInputStream readHeader() allocates two new 4 MiB block buffers whenever a maximum-block-size frame header is read, and the default concatenated-frame mode allows attacker-controlled streams containing many minimal empty frames to trigger roughly 8 MiB of allocation for every 11 input bytes. The stream produces no decompressed output while consuming CPU and garbage-collection time, so decompressed-size limits do not mitigate the issue; readSingleFrame mode is not affected. This issue is fixed in version 1.11.4.

CVSS Base Scores

version 3.1