CVE-2026-106453: yawkat LZ4 Java LZ4DecompressorWithLength Allocates The Unvalidated Size Vulnerability

MODERATE
Advisory Identifier: GHSA-6cx8-rjf8-pr8g
CVSS 5.3
CWE-789
Published
Advisory Summary

CVE-2026-106453 is a MODERATE (CVSS 5.3) lz4decompressorwithlength allocates the unvalidated size vulnerability (CWE-789: Memory Allocation with Excessive Size Value) affecting yawkat LZ4 Java libraries in the Maven ecosystem. The issue involves lz4decompressorwithlength allocates the unvalidated size from the 4-byte length header, so a 5-byte input triggers a 1 gib allocation and outofmemoryerror. Remediation is available by upgrading affected packages to version 1.11.2.

CVE-2026-106453 at a Glance

CVE Identifier CVE-2026-106453
GHSA Identifier GHSA-6cx8-rjf8-pr8g
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-789: Memory Allocation with Excessive Size Value
Affected Product yawkat LZ4 Java
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability Low (A:L)

How to Fix CVE-2026-106453

To remediate this vulnerability, upgrade all affected yawkat LZ4 Java dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

at.yawk.lz4:lz4-java fixed: 1.11.2
<dependency>
    <groupId>at.yawk.lz4</groupId>
    <artifactId>lz4-java</artifactId>
    <version>1.11.2</version>
</dependency>
org.lz4:lz4-java fixed: Latest secure release
<dependency>
    <groupId>org.lz4</groupId>
    <artifactId>lz4-java</artifactId>
    <version>Latest secure release</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=at.yawk.lz4

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-106453, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=at.yawk.lz4

Analyze the terminal output to locate any version of yawkat LZ4 Java in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.11.2), your application is affected.

Note: The mvn dependency:tree -Dincludes=at.yawk.lz4 command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-789: Memory Allocation with Excessive Size Value, where the product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. In yawkat LZ4 Java, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary `LZ4DecompressorWithLength.decompress(byte[], int)` allocates whatever size the 4-byte length header declares, before it reads a single byte of compressed data. A 5-byte input whose header says `0x40000000` makes the JVM commit a gigabyte and can cause heap exhaustion. ### Details `net.jpountz.lz4.LZ4DecompressorWithLength` reads the header and passes it straight on: ```java final int destLen = getDecompressedLength(src, srcOff); return fastDecompressor.decompress(src, srcOff + 4, destLen); ``` and `net.jpountz.lz4.LZ4FastDecompressor` allocates it: ```java public final byte[] decompress(byte[] src, int srcOff, int destLen) { final byte[] decompressed = new byte[destLen]; decompress(src, srcOff, decompressed, 0, destLen); return decompressed; } ``` `getDecompressedLength` performs no validation: no comparison against `src.length`, no ceiling, no rejection of negatives. `LZ4SafeDecompressor.decompress(byte[], int, int, int)` has the same shape with `maxDestLen`. The sibling overload that callers pass their own buffer to, `decompress(src, srcOff, dest, destOff, destLen)`, is fine, because there `destLen` is chosen by the caller rather than by the input. The bug is specific to the convenience overloads that take the size from the header, and that difference is the whole finding. ### Impact Any application that decompresses attacker-supplied LZ4 frames through the with-length convenience API can be made to allocate up to 2 GiB per call from a 5-byte message. On a service that decompresses request bodies, a few concurrent 5-byte requests exhaust the heap. No privileges are needed, only the ability to get bytes into the decompressor. Confidentiality and integrity are untouched.

CVE-2026-106453 Affected yawkat LZ4 Java Versions

2 component(s)
Fixed Versions:
1.11.2
Product / Package Ecosystem Affected Versions Fixed Version
at.yawk.lz4:lz4-java
Maven
< 1.11.2
1.11.2
org.lz4:lz4-java
Maven
≤ 1.8.1

References

Frequently Asked Questions

What is CVE-2026-106453?
CVE-2026-106453 is a security vulnerability in yawkat LZ4 Java involving LZ4DecompressorWithLength allocates the unvalidated size from the 4-byte length header, so a 5-byte input triggers a 1 GiB allocation and OutOfMemoryError under CWE-789: Memory Allocation with Excessive Size Value.
Which yawkat LZ4 Java versions are affected?
Affected versions include releases prior to 1.11.2 across affected packages: at.yawk.lz4:lz4-java, org.lz4:lz4-java.
What version fixes CVE-2026-106453?
Upgrading to 1.11.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is lz4-java affected?
Yes, at.yawk.lz4:lz4-java is affected in releases prior to 1.11.2, Latest secure release. Upgrade your dependency to 1.11.2, Latest secure release or later.
What is the CVSS score of CVE-2026-106453?
CVE-2026-106453 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2026-106453?
CVE-2026-106453 is classified under CWE-789: Memory Allocation with Excessive Size Value (The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.).
How can I check Maven dependencies for CVE-2026-106453?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=at.yawk.lz4'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-6cx8-rjf8-pr8g",
  "modified" : "2026-10-07T16:17:48Z",
  "published" : "2026-10-07T16:17:47Z",
  "aliases" : [ "CVE-2026-106453" ],
  "summary" : "yawkat LZ4 Java: LZ4DecompressorWithLength allocates the unvalidated size from the 4-byte length header, so a 5-byte input triggers a 1 GiB allocation and OutOfMemoryError",
  "details" : "### Summary\n\n`LZ4DecompressorWithLength.decompress(byte[], int)` allocates whatever size the 4-byte length header declares, before it reads a single byte of compressed data. A 5-byte input whose header says `0x40000000` makes the JVM commit a gigabyte and can cause heap exhaustion.\n\n### Details\n\n`net.jpountz.lz4.LZ4DecompressorWithLength` reads the header and passes it straight on:\n\n```java\nfinal int destLen = getDecompressedLength(src, srcOff);\nreturn fastDecompressor.decompress(src, srcOff + 4, destLen);\n```\n\nand `net.jpountz.lz4.LZ4FastDecompressor` allocates it:\n\n```java\npublic final byte[] decompress(byte[] src, int srcOff, int destLen) {\n  final byte[] decompressed = new byte[destLen];\n  decompress(src, srcOff, decompressed, 0, destLen);\n  return decompressed;\n}\n```\n\n`getDecompressedLength` performs no validation: no comparison against `src.length`, no ceiling, no rejection of negatives. `LZ4SafeDecompressor.decompress(byte[], int, int, int)` has the same shape with `maxDestLen`.\n\nThe sibling overload that callers pass their own buffer to, `decompress(src, srcOff, dest, destOff, destLen)`, is fine, because there `destLen` is chosen by the caller rather than by the input. The bug is specific to the convenience overloads that take the size from the header, and that difference is the whole finding.\n\n### Impact\n\nAny application that decompresses attacker-supplied LZ4 frames through the with-length convenience API can be made to allocate up to 2 GiB per call from a 5-byte message. On a service that decompresses request bodies, a few concurrent 5-byte requests exhaust the heap. No privileges are needed, only the ability to get bytes into the decompressor. Confidentiality and integrity are untouched.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "at.yawk.lz4:lz4-java"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.11.2"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.11.1"
    }
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.lz4:lz4-java"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "1.8.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/yawkat/lz4-java/security/advisories/GHSA-6cx8-rjf8-pr8g"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-106453"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/yawkat/lz4-java/commit/6492ce5aca6bd03ff9e08ee18a2beb94c431371a"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/yawkat/lz4-java"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/yawkat/lz4-java/releases/tag/v1.11.2"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-789" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-07T16:17:47Z",
    "nvd_published_at" : "2026-10-06T20:17:27Z"
  }
}