CVE-2026-106450: yawkat LZ4 Java LZ4FrameInputStream Reallocates Block Buffers For Vulnerability
MODERATECVE-2026-106450 is a MODERATE (CVSS 5.3) lz4frameinputstream reallocates block buffers for vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting yawkat LZ4 Java libraries in the Maven ecosystem. The issue involves lz4frameinputstream reallocates block buffers for every frame, allowing cpu and gc amplification from small inputs. Remediation is available by upgrading affected packages to version 1.11.4.
CVE-2026-106450 at a Glance
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).
How to Fix CVE-2026-106450
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.
<dependency>
<groupId>at.yawk.lz4</groupId>
<artifactId>lz4-java</artifactId>
<version>1.11.4</version>
</dependency>
<dependency>
<groupId>org.lz4</groupId>
<artifactId>lz4-java</artifactId>
<version>Latest secure release</version>
</dependency>
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-106450, 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.4), 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-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can 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
CVE-2026-106450 Affected yawkat LZ4 Java Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
at.yawk.lz4:lz4-java
|
Maven |
< 1.11.4
|
1.11.4
|
|
org.lz4:lz4-java
|
Maven |
≤ 1.8.1
|
|
References
Frequently Asked Questions
What is CVE-2026-106450?
Which yawkat LZ4 Java versions are affected?
What version fixes CVE-2026-106450?
Is lz4-java affected?
What is the CVSS score of CVE-2026-106450?
What CWE is associated with CVE-2026-106450?
How can I check Maven dependencies for CVE-2026-106450?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-gm45-99xc-r7wv",
"modified" : "2026-10-07T20:35:40Z",
"published" : "2026-10-07T20:35:40Z",
"aliases" : [ "CVE-2026-106450" ],
"summary" : "yawkat LZ4 Java: LZ4FrameInputStream reallocates block buffers for every frame, allowing CPU and GC amplification from small inputs",
"details" : "### Summary\n\n`LZ4FrameInputStream` allocates two new buffers of the frame's maximum block size, up to 4 MiB each, every time it reads a frame header. Because concatenated frames are read by default, an input made of many minimal empty frames forces about 8 MiB of zeroed heap allocation for every 11 input bytes.\n\n### Details\n\nIn `net.jpountz.lz4.LZ4FrameInputStream.readHeader()`:\n\n```java\nmaxBlockSize = frameInfo.getBD().getBlockMaximumSize();\ncompressedBuffer = new byte[maxBlockSize]; // Reused during different compressions\nrawBuffer = new byte[maxBlockSize];\nbuffer = ByteBuffer.wrap(rawBuffer);\n```\n\nThis runs for every frame, and the previous frame's arrays are never reused. A valid 11-byte frame consists of the magic number, FLG `0x60`, BD `0x70` (4 MiB blocks), the header checksum, and an immediate end mark. It carries no data, yet triggers the full 8 MiB allocation. `new LZ4FrameInputStream(in)` reads concatenated frames by default.\n\nIn local measurements on JDK 25, 10,000 such frames (110 KB of input) took about 8 seconds of CPU to read, roughly 70 seconds per MiB of input. This was similar under G1, Parallel, Serial and ZGC. A legitimate stream costs orders of magnitude less per input byte.\n\n### Impact\n\nApplications that decode attacker-controlled LZ4 frame data with `LZ4FrameInputStream` can be made to spend large amounts of CPU and GC time relative to the input size. Live heap stays bounded at about 8 MiB and the stream produces no output, so decompressed-size limits do not help. Cost grows linearly with input size, so the practical limit is the compressed input size the application accepts. Availability impact only.\n\nApplications using `readSingleFrame = true` perform only one allocation and are not affected.\n\n### Patch\n\nFixed in lz4-java 1.11.4. `LZ4FrameInputStream` now allocates its block buffers only when a block needs them and reuses them across frames, never shrinking them. The content checksum hash and the skippable-frame skip buffer are also reused instead of being created for every frame. Decompression is limited to the current frame's maximum block size.\n\nFor older versions, the workaround is to limit the compressed input size accepted from untrusted sources, or use single-frame mode where that is sufficient.",
"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.4"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.11.3"
}
}, {
"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-gm45-99xc-r7wv"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-106450"
}, {
"type" : "WEB",
"url" : "https://github.com/yawkat/lz4-java/commit/2acc0ec1ead226145c62a817c18c8ed49233a283"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/yawkat/lz4-java"
}, {
"type" : "WEB",
"url" : "https://github.com/yawkat/lz4-java/releases/tag/v1.11.4"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-770" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-10-07T20:35:40Z",
"nvd_published_at" : "2026-10-06T20:17:27Z"
}
}