Patch Forecast
Yellow warning
Plan into this sprint.

CVE-2026-106450 · GHSA-gm45-99xc-r7wv

yawkat LZ4 Java: LZ4FrameInputStream reallocates block buffers for every frame, allowing CPU and GC amplification from small inputs

Risk score
43/100
CVSS
5.3 v3.1
Exploit chance (30 days)
0.4%
Published
6 Oct 2026

Open in the live forecast Today's forecast

What to know

What it is
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 …
Affected
at.yawk.lz4:lz4-java (maven) <= 1.11.3; org.lz4:lz4-java (maven) <= 1.8.1
Fix
Upgrade at.yawk.lz4:lz4-java to 1.11.4 or later.
Exploitation
No known exploitation

Why it is Yellow

  • CVSS 5.3 medium
  • On your watchlist: Maven

Affected packages

PackageEcosystemVulnerableFixed in
at.yawk.lz4:lz4-javamaven<= 1.11.31.11.4
org.lz4:lz4-javamaven<= 1.8.1No fix yet

References

Original 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.

Last activity 6 Oct 2026. Patch Forecast updates every hour.