WaratekVRT Sign in

CVE-2026-106449

Severity3.7 Low CVSS 3.1
Fixed in1.11.4
WeaknessCWE-674
Published6 Oct 2026
Updated7 Oct 2026

Published 39 days ago. NVD often adds the list of affected products days or weeks after a CVE is published, and the other sources we check lag too. The scope and status here may change.

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.

Exploitation status

No public exploit

No exploit has been reported in the sources we check.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment exploitation: none
  • Indexed PoC none indexed
  • EPSS 0.42% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: yawkat/lz4-java c8ebf97.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory
Finding This CVE is LOW severity, is not listed in CISA KEV or VulnCheck KEV, has no public exploit or PoC in any indexed source, carries no CISA Vulnrichment finding of a demonstrated exploit, and is not part of an Oracle Critical Patch Update. None of the signals that would put it in front of an engineer is present, and the volume of CVEs below that bar is too great to take one at a time, so no rule is written for it. This is a decision about what we act on, not a finding that the CVE is harmless — a patch may well be derivable, and a low-severity defect can still be one link in a longer chain.
Candidate fix https://github.com/yawkat/lz4-java/commit/c8ebf97d504fb34434fda46fc761e8202570e0d8 : a commit: the change itself

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
at.yawk.lz4:lz4-java 0 1.11.4 unbounded
org.lz4:lz4-java 0 none 1.8.1

Products and versions

2 products, 2 version entries
SourceVendorProductSchemeAffected versions
osv at.yawk.lz4 lz4-java generic < 1.11.4
osv org.lz4 lz4-java generic ≤ 1.8.1

References

URLTags
https://github.com/yawkat/lz4-java/commit/c8ebf97d504fb34434fda46fc761e8202570e0d8 commit
https://github.com/yawkat/lz4-java/security/advisories/GHSA-343h-94h5-c4wr WEB
https://github.com/yawkat/lz4-java PACKAGE
https://github.com/yawkat/lz4-java/releases/tag/v1.11.4 WEB

Timeline

Published2026-10-06By the CVE Program.
NVD record modified2026-10-07NVD's own last-modified date for this record.