CVE-2026-106449: yawkat lz4-java · Uncontrolled Recursion
Affects yawkat lz4-javaSource CVE Database V5
Not known to be exploited · CVSS 3.7 Low : upgrade to 1.11.4 when convenient.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.11.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.
What to do
Upgrade lz4-java and com.github.yawkat/lz4-java to 1.11.4.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| yawkatlz4-java | Affected
| Fixed in
|
Mavencom.github.yawkat/lz4-javapkg:maven/com.github.yawkat/lz4-javaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in lz4-java version 1.11.4, which replaces recursion with iteration to prevent stack exhaustion. For older versions, use the default stopOnEmptyBlock=true setting when processing untrusted input or catch StackOverflowError around the read loop to handle this condition.
Description
yawkat LZ4 Java provides LZ4 compression for Java. Prior to 1.11.4, net.jpountz.lz4.LZ4BlockInputStream configured with stopOnEmptyBlock set to false handles each well-formed empty LZ4Block by recursively calling refill(), allowing a long sequence of empty blocks in an attacker-controlled compressed stream to exhaust the decoding thread's stack and throw StackOverflowError. The default stopOnEmptyBlock setting is true and is not affected, and the issue does not cause memory corruption. This issue is fixed in version 1.11.4.