Quick answers
- Is CVE-2026-106453 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106453 being exploited in the wild.
- How severe is CVE-2026-106453?
- 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.1, ECOSYSTEM:introduced=0,fixed=1.11.2; org.lz4:lz4-java (Maven) <= 1.8.1, ECOSYSTEM:introduced=0,last_affected=1.8.1; Yawkat LZ4 Java before 1.11.2.
- Is there a fix for CVE-2026-106453?
- Yes. at.yawk.lz4:lz4-java (Maven): upgrade to 1.11.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106453 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106453?
- 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.2 or later
# set at.yawk.lz4:lz4-java to 1.11.2 in your pom.xml or build.gradle
Technical details
LZ4DecompressorWithLength reads a four-byte length header from compressed input and allocates memory for decompression before validating the actual compressed payload, allowing a five-byte attacker input to trigger allocation of up to 2 GiB. The vulnerability affects convenience overloads using LZ4FastDecompressor or LZ4SafeDecompressor; overloads that write to caller-provided buffers are unaffected since the caller controls allocation. The fix validates the declared length against the actual compressed data before allocating memory.
Affected products
- yawkat LZ4 Java before 1.11.2
Identifiers
- CVE-2026-106453
- GHSA-6cx8-rjf8-pr8g
Timeline
- 2026-08-06: disclosed
- 2026-08-06: patched
- 2026-10-06: advisory