Quick answers
- Is CVE-2026-106450 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106450 being exploited in the wild.
- How severe is CVE-2026-106450?
- Medium severity, with a CVSS score of 5.3, published 6 October 2026.
- Which products and versions are affected?
- at.yawk.lz4:lz4-java (Maven) <= 1.11.3, ECOSYSTEM:introduced=0,fixed=1.11.4; org.lz4:lz4-java (Maven) <= 1.8.1, ECOSYSTEM:introduced=0,last_affected=1.8.1; Yawkat LZ4 Java prior to 1.11.4.
- Is there a fix for CVE-2026-106450?
- Yes. at.yawk.lz4:lz4-java (Maven): upgrade to 1.11.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106450 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-106450?
- Check whether you run at.yawk.lz4:lz4-java (Maven), org.lz4:lz4-java (Maven) or Yawkat LZ4 Java at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- at.yawk.lz4:lz4-java (Maven): upgrade to 1.11.4 or later
# set at.yawk.lz4:lz4-java to 1.11.4 in your pom.xml or build.gradle
Technical details
The LZ4FrameInputStream.readHeader() method allocates two 4 MiB block buffers for each maximum-block-size frame header encountered. In concatenated-frame mode (the default), an attacker can send many minimal empty frames that trigger approximately 8 MiB of memory allocation per 11 input bytes, causing resource exhaustion and denial of service through memory pressure and garbage collection overhead. The single-frame mode is unaffected, and decompressed-size limits do not mitigate the issue since no output is produced.
Affected products
- yawkat LZ4 Java prior to 1.11.4
Identifiers
- CVE-2026-106450
- GHSA-gm45-99xc-r7wv
Timeline
- 2026-10-06: disclosed
- 2026-09-25: patched