Uncontrolled Memory Allocation Affecting logstash-8 package, versions *


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-LOGSTASH8-20656285
  • published9 Oct 2026
  • disclosed6 Oct 2026

Introduced: 6 Oct 2026

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

How to fix?

There is no fixed version for Minimos:latest logstash-8.

NVD Description

Note: Versions mentioned in the description apply only to the upstream logstash-8 package and not the logstash-8 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, net.jpountz.lz4.LZ4BlockInputStream refill() validates that the compressedLen field in a legacy LZ4Block header is nonnegative but allocates a compressed-input buffer of that attacker-controlled size before reading payload data, allowing a header-only stream to request a near-2 GiB allocation and exhaust the JVM heap. Canonical writers emit raw blocks when compression is not smaller than the original block, but vulnerable readers accept non-canonical oversized compressed blocks. This issue is fixed in version 1.11.2.

CVSS Base Scores

version 3.1