Uncontrolled Memory Allocation Affecting kafka-4.2 package, versions <4.2.2-r0


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-MINIMOSLATEST-KAFKA42-20655386
  • published9 Oct 2026
  • disclosed6 Oct 2026

Introduced: 6 Oct 2026

NewCVE-2026-106453  (opens in a new tab)
CWE-789  (opens in a new tab)

How to fix?

Upgrade Minimos:latest kafka-4.2 to version 4.2.2-r0 or higher.

NVD Description

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

yawkat LZ4 Java provides LZ4 compression for Java. Prior to 1.11.2, LZ4DecompressorWithLength uses getDecompressedLength to trust the four-byte decompressed-length header before validating the compressed input, allowing a five-byte attacker-supplied input whose header declares a large output size to request up to approximately 2 GiB and exhaust the JVM heap. Convenience overloads backed by LZ4FastDecompressor or LZ4SafeDecompressor allocate the untrusted size, while overloads that write to a caller-provided destination buffer are not affected because the caller controls the destination size. This issue is fixed in version 1.11.2.

CVSS Base Scores

version 3.1