Skip to main content
VulnerabilityPublished

CVE-2026-106453: yawkat lz4-java · Excessive Memory Allocation

Affects yawkat lz4-javaSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 1.11.2 when convenient.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.11.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade lz4-java and com.github.yawkat/lz4-java to 1.11.2.

Affected software

ProductAffectedFixed in
yawkatlz4-javaAffected
  • <1.11.2
Fixed in
  • 1.11.2
Mavencom.github.yawkat/lz4-javapkg:maven/com.github.yawkat/lz4-javaOther threatsAffected
  • <1.11.2
Fixed in
  • 1.11.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to yawkat lz4-java version 1.11.2 or later where this issue is fixed. Avoid using convenience overloads that allocate memory based on untrusted decompressed-length headers. Use overloads that write to caller-provided destination buffers to mitigate risk if upgrading is not immediately possible.

Description

yawkat LZ4 Java provides LZ4 compression for Java. Prior to 1.11.2, LZ4DecompressorWithLength uses getDecompressedLength to trust the four-byte decompressed-length header before validating the compressed input, allowing a five-byte attacker-supplied input whose header declares a large output size to request up to approximately 2 GiB and exhaust the JVM heap. Convenience overloads backed by LZ4FastDecompressor or LZ4SafeDecompressor allocate the untrusted size, while overloads that write to a caller-provided destination buffer are not affected because the caller controls the destination size. This issue is fixed in version 1.11.2.

References

Community reviews

Loading reviews…