WaratekVRT Sign in

CVE-2026-106450

Severity5.3 Medium CVSS 3.1
Fixed in1.11.4
WeaknessCWE-770
Published6 Oct 2026
Updated9 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.LZ4FrameInputStream readHeader() allocates two new 4 MiB block buffers whenever a maximum-block-size frame header is read, and the default concatenated-frame mode allows attacker-controlled streams containing many minimal empty frames to trigger roughly 8 MiB of allocation for every 11 input bytes. The stream produces no decompressed output while consuming CPU and garbage-collection time, so decompressed-size limits do not mitigate the issue; readSingleFrame mode is not affected. 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.45% 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 2acc0ec.

  • 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 MEDIUM 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/2acc0ec1ead226145c62a817c18c8ed49233a283 : 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/2acc0ec1ead226145c62a817c18c8ed49233a283 commit
https://github.com/yawkat/lz4-java/security/advisories/GHSA-gm45-99xc-r7wv 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-09NVD's own last-modified date for this record.