CVE-2026-106453: CWE-789: Memory Allocation with Excessive Size Value in yawkat lz4-java
Description
A memory allocation vulnerability exists in yawkat lz4-java prior to version 1.11.2. The LZ4DecompressorWithLength component trusts a decompressed-length header from input data without validating it, allowing an attacker to specify a large output size. This can cause the JVM heap to be exhausted by allocating up to approximately 2 GiB of memory. Overloads that write to a caller-provided buffer are not affected. The issue is fixed in version 1.11.2.
CVSS v3.1
Score 5.3medium
Affected software
yawkat
lz4-java
pkg:maven/com.github.yawkat/lz4-javaRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
yawkat lz4-java versions before 1.11.2 contain a vulnerability (CWE-789) where the LZ4DecompressorWithLength uses the decompressed-length header from input data to allocate memory without validating the compressed input size. An attacker can supply a crafted five-byte input with a large decompressed-length header, causing the decompressor to allocate up to about 2 GiB of memory, potentially exhausting the JVM heap. Convenience overloads that rely on LZ4FastDecompressor or LZ4SafeDecompressor are affected, while overloads that write to a caller-provided destination buffer are not vulnerable because the caller controls the buffer size. This vulnerability has a CVSS 3.1 score of 5.3 (medium severity) and was fixed in version 1.11.2.
Potential Impact
An attacker can cause a denial of service by exhausting the JVM heap memory through excessive memory allocation during decompression. This does not affect confidentiality or integrity but impacts availability by potentially crashing or severely degrading the performance of the Java application using the vulnerable lz4-java library.
Mitigation Recommendations
Upgrade to yawkat lz4-java version 1.11.2 or later, where this vulnerability is fixed. Avoid using convenience overloads that allocate memory based on untrusted decompressed-length headers. Use overloads that write to caller-provided destination buffers, as they are not affected by this issue.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-10-06T16:49:40.591Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ac5544a2cdf04f656d9e128
Added to database: 10/06/2026, 20:04:26 UTC
Last enriched: 10/06/2026, 20:19:22 UTC
Last updated: 10/06/2026, 20:19:22 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.