Skip to main content
Vulnerability Database/CVE-2026-106453

CVE-2026-106453: LZ4 Java Denial of Service Vulnerability

CVE-2026-106453 is a denial of service vulnerability in yawkat LZ4 Java that allows attackers to exhaust JVM heap memory through malicious input. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-106453 Overview

CVE-2026-106453 is a memory allocation vulnerability in yawkat lz4-java, a Java library that provides LZ4 compression and decompression. Versions prior to 1.11.2 trust an attacker-controlled four-byte decompressed-length header in LZ4DecompressorWithLength before validating the compressed input. A five-byte malicious input can declare an output size of approximately 2 GiB, causing the Java Virtual Machine (JVM) to allocate memory sized to the untrusted value and exhaust the heap. The flaw is tracked under [CWE-789: Memory Allocation with Excessive Size Value] and resolved in version 1.11.2.

Critical Impact

A single five-byte input can trigger a ~2 GiB heap allocation, exhausting JVM memory and causing denial of service in applications that decompress untrusted LZ4 payloads.

Affected Products

  • yawkat lz4-java versions prior to 1.11.2
  • Applications using LZ4DecompressorWithLength with LZ4FastDecompressor convenience overloads
  • Applications using LZ4DecompressorWithLength with LZ4SafeDecompressor convenience overloads

Discovery Timeline

  • 2026-10-06 - CVE-2026-106453 published to the National Vulnerability Database (NVD)
  • 2026-10-07 - Last updated in NVD database

Technical Details for CVE-2026-106453

Vulnerability Analysis

The vulnerability resides in LZ4DecompressorWithLength, a helper class that reads a four-byte length prefix from the compressed stream to determine the destination buffer size. The class calls getDecompressedLength to extract this header, then allocates a destination array of that size before verifying that the compressed payload can actually produce that much output.

An attacker who controls the compressed input can supply a five-byte message consisting of a four-byte length field declaring a value near Integer.MAX_VALUE and a single byte of compressed data. The library allocates a byte array sized to the attacker-declared value, which can approach 2 GiB, before any decompression occurs. In most JVM configurations this exhausts the heap and raises OutOfMemoryError, terminating request handlers or the entire process.

The issue affects convenience overloads backed by LZ4FastDecompressor and LZ4SafeDecompressor, which allocate the destination buffer internally. Overloads that accept a caller-provided destination buffer are not affected, because the caller controls allocation.

Root Cause

The root cause is unvalidated trust in an attacker-controlled size value. LZ4DecompressorWithLength performs no sanity check comparing the declared decompressed length against the actual compressed input size or against a configured upper bound. This matches the pattern described by CWE-789: Memory Allocation with Excessive Size Value.

Attack Vector

Exploitation requires only that a vulnerable application decompresses attacker-supplied LZ4 data using an affected convenience overload. The attack vector is network-reachable in any service that accepts compressed uploads, message payloads, or RPC bodies and routes them through LZ4DecompressorWithLength. No authentication or user interaction is required when the decompression endpoint is exposed.

See the GitHub Security Advisory GHSA-6cx8-rjf8-pr8g for the vendor description. No public proof-of-concept exploit code is referenced in the advisory.

Detection Methods for CVE-2026-106453

Indicators of Compromise

  • Repeated java.lang.OutOfMemoryError: Java heap space exceptions originating from net.jpountz.lz4.LZ4DecompressorWithLength or related call sites
  • Sudden JVM heap growth to configured maximum followed by process restart or hang when handling LZ4-compressed inputs
  • Short compressed payloads (five to a few dozen bytes) arriving on endpoints that accept LZ4 data

Detection Strategies

  • Perform software composition analysis (SCA) on Java build manifests to identify org.lz4:lz4-java or shaded copies at versions below 1.11.2
  • Instrument decompression entry points to log the declared decompressed length and compare it against the compressed payload size, flagging large ratios
  • Correlate application OutOfMemoryError events with inbound request metadata to identify attacker-controlled sources

Monitoring Recommendations

  • Monitor JVM heap utilization and garbage collection pauses on services that process compressed input from untrusted sources
  • Alert on process restarts of Java services that coincide with inbound traffic to decompression endpoints
  • Track dependency inventories for lz4-java and transitive inclusions through frameworks that bundle it

How to Mitigate CVE-2026-106453

Immediate Actions Required

  • Upgrade yawkat lz4-java to version 1.11.2 or later across all affected applications and container images
  • Audit code paths that pass attacker-controlled data into LZ4DecompressorWithLength convenience overloads
  • Enforce request size limits at the ingress layer so that compressed payloads cannot reach vulnerable code when oversized

Patch Information

The fix is published in yawkat lz4-java release v1.11.2. The patch is implemented in commit 6492ce5, which validates the declared decompressed length against the available compressed input before allocating the destination buffer. Update the Maven or Gradle dependency coordinate to 1.11.2 and rebuild all downstream artifacts.

Workarounds

  • Switch to decompression overloads that accept a caller-provided destination buffer, since those are not affected
  • Wrap calls to LZ4DecompressorWithLength with an explicit upper bound check on the declared decompressed length before invoking the library
  • Constrain JVM heap settings and container memory limits so a single process failure does not propagate across the service
bash
# Maven dependency update example
# pom.xml
# <dependency>
#   <groupId>org.lz4</groupId>
#   <artifactId>lz4-java</artifactId>
#   <version>1.11.2</version>
# </dependency>

mvn versions:use-dep-version -Dincludes=org.lz4:lz4-java -DdepVersion=1.11.2 -DforceVersion=true
mvn dependency:tree | grep lz4-java

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.