Vulnerability DatabaseCVE-2026-106449

CVE-2026-106449: 
Java vulnerability analysis and mitigation

Overview

CVE-2026-106449 is a Denial of Service vulnerability in yawkat LZ4 Java (lz4-java) caused by uncontrolled recursion in LZ4BlockInputStream when configured with stopOnEmptyBlock=false. An unauthenticated remote attacker can craft a compressed stream containing a long sequence of empty LZ4 blocks to exhaust the decoding thread's stack and trigger a StackOverflowError. Affected versions are at.yawk.lz4:lz4-java ≤ 1.11.3 and org.lz4:lz4-java ≤ 1.8.1; the default configuration (stopOnEmptyBlock=true) is not affected. The vulnerability was published on September 25, 2026, and carries a CVSS v3.1 base score of 3.7 (Low) (Github Advisory, Red Hat Bugzilla).

Technical details

The root cause is uncontrolled recursion (CWE-674) in net.jpountz.lz4.LZ4BlockInputStream.refill(). When stopOnEmptyBlock is set to false (used for reading concatenated block streams), the method handles each well-formed empty LZ4 block (21 bytes each) by calling itself recursively with no depth limit. Approximately 10,000 to 100,000 consecutive empty blocks — totaling roughly 210 KB to 2.1 MB of crafted input — are sufficient to overflow the thread stack and throw a StackOverflowError. Because StackOverflowError is a Java Error rather than an IOException, callers that only catch I/O exceptions for corrupt input will not handle it, potentially causing unhandled crashes. The fix in version 1.11.4 replaces the recursive call with an iterative loop, ensuring constant stack usage regardless of the number of empty blocks (Github Advisory, Patch Commit).

Impact

Exploitation results in a StackOverflowError that crashes the decoding thread, causing a Denial of Service for any application processing attacker-controlled LZ4Block streams with stopOnEmptyBlock=false. There is no confidentiality or integrity impact, and no memory corruption occurs. The scope is limited to the availability of the affected decoding service or thread, but in applications where LZ4 decompression is on a critical processing path, this could render the service unavailable (Github Advisory, Red Hat Bugzilla).

Exploitability

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at this time (Github Advisory). The EPSS score is approximately 0.339% (26th percentile), indicating a low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires high attack complexity, as the attacker must be able to supply a crafted compressed stream to an application specifically configured with stopOnEmptyBlock=false, which is a non-default setting.

Exploitation steps

  1. Identify target: Locate an application that uses at.yawk.lz4:lz4-java ≤ 1.11.3 or org.lz4:lz4-java ≤ 1.8.1 and accepts attacker-controlled compressed data for decompression with LZ4BlockInputStream configured with stopOnEmptyBlock=false.
  2. Craft malicious stream: Construct a byte stream consisting of a long sequence of well-formed empty LZ4 blocks (each 21 bytes, containing the LZ4 magic bytes, compression method byte, and zero-length fields). Approximately 10,000–100,000 empty blocks (210 KB–2.1 MB total) are sufficient to trigger the overflow, depending on JVM stack size and JIT state.
  3. Submit crafted stream: Deliver the malicious compressed stream to the target application through whatever input channel it exposes (e.g., HTTP upload, message queue, network socket, file upload).
  4. Trigger StackOverflowError: The application's LZ4BlockInputStream.refill() method recursively calls itself once per empty block with no depth limit, exhausting the thread stack and throwing StackOverflowError, crashing the decoding thread and causing a Denial of Service (Github Advisory, Patch Commit).

Indicators of compromise

  • Logs: Java application logs showing uncaught java.lang.StackOverflowError originating from net.jpountz.lz4.LZ4BlockInputStream.refill() or readBlock(); thread dump entries showing deep recursive call stacks in LZ4BlockInputStream.
  • Application Behavior: Sudden crashes or unresponsiveness of services that perform LZ4 decompression; repeated thread failures in application server logs (e.g., Tomcat, Netty) associated with LZ4 stream processing.
  • Network: Inbound requests or data streams containing large payloads (210 KB–2.1 MB) composed of repetitive 21-byte patterns consistent with empty LZ4 blocks, particularly if the application does not normally receive such input sizes.

Mitigation and workarounds

Upgrade at.yawk.lz4:lz4-java to version 1.11.4 or later, which fixes the issue by replacing the recursive refill() call with an iterative loop (lz4-java v1.11.4). For applications that cannot upgrade immediately, two workarounds are available: (1) ensure LZ4BlockInputStream uses the default stopOnEmptyBlock=true configuration for any untrusted input, or (2) wrap the read loop with a catch (StackOverflowError e) block to prevent unhandled crashes. Note that org.lz4:lz4-java ≤ 1.8.1 has no patched version available under that artifact ID, so migration to at.yawk.lz4:lz4-java 1.11.4 is recommended (Github Advisory).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Affected

bookworm

lz4-java

Affected

sid

lz4-java

Affected

trixie

lz4-java

Affected

Ubuntu

Unknown

devel

lz4-java

Unknown

focal (esm-apps)

lz4-java

Unknown

jammy

lz4-java

Unknown

jammy (esm-apps)

lz4-java

Unknown

noble

lz4-java

Unknown

noble (esm-apps)

lz4-java

Unknown

resolute

lz4-java

Unknown

resolute (esm-apps)

lz4-java

Unknown

RHEL / CentOS

Affected

RHEL 9

jmc.src

Affected

Source: This report was generated using AI

Related Java vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-61827HIGH8.7
  • Java logoJava
  • io.netty.incubator:netty-incubator-codec-bhttp
NoYesNov 19, 2026
CVE-2026-63202HIGH7.5
  • Java logoJava
  • io.netty.incubator:netty-incubator-codec-bhttp
NoYesNov 19, 2026
CVE-2026-63124HIGH7.5
  • Java logoJava
  • io.netty.incubator:netty-incubator-codec-bhttp
NoYesNov 19, 2026
CVE-2026-69133MEDIUM5.3
  • Java logoJava
  • io.netty.incubator:netty-incubator-codec-ohttp
NoYesNov 19, 2026
CVE-2026-61799MEDIUM5.3
  • Java logoJava
  • io.netty.incubator:netty-incubator-codec-bhttp
NoYesNov 19, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management