CVE-2026-106450: CWE-770: Allocation of Resources Without Limits or Throttling in yawkat lz4-java
Description
yawkat lz4-java versions prior to 1.11.4 have a resource allocation vulnerability in the LZ4FrameInputStream readHeader() method. When processing maximum-block-size frame headers in concatenated-frame mode, the code allocates two 4 MiB buffers per frame, allowing attacker-controlled streams with many minimal empty frames to cause excessive memory allocation and CPU consumption without producing decompressed output. This can lead to denial of service due to resource exhaustion. The issue does not affect readSingleFrame mode and is fixed in version 1.11.4.
CVSS v3.1
Score 5.3medium
Affected software
yawkat
lz4-java
Run 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
The yawkat lz4-java library before version 1.11.4 contains a CWE-770 vulnerability where the LZ4FrameInputStream readHeader() method allocates two 4 MiB block buffers for each maximum-block-size frame header read. In concatenated-frame mode, an attacker can craft streams with many minimal empty frames, causing roughly 8 MiB of memory allocation for every 11 bytes of input. This excessive allocation consumes CPU and garbage collection resources without producing decompressed output, leading to potential denial of service. The vulnerability is resolved in version 1.11.4.
Potential Impact
An attacker can cause the application using vulnerable versions of yawkat lz4-java to allocate excessive memory and CPU resources by sending specially crafted compressed streams. This can degrade performance or cause denial of service due to resource exhaustion. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
Upgrade to yawkat lz4-java version 1.11.4 or later, where this issue is fixed. No other mitigations are indicated. The readSingleFrame mode is not affected, but switching modes is not a recommended primary mitigation.
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: 6ac5544a2cdf04f656d9e12e
Added to database: 10/06/2026, 20:04:26 UTC
Last enriched: 10/06/2026, 20:18:53 UTC
Last updated: 10/06/2026, 20:19:15 UTC
Views: 3
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.