Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-106453— yawkat LZ4 Java: LZ4DecompressorWithLength allocates the unvalidated size from the 4-byte length header, so a 5-byte input triggers a 1 GiB allocation and OutOfMemoryError

Quick assessment

Affected
yawkat lz4-java
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

yawkat LZ4 Java 为 Java 提供了 LZ4 压缩功能。在 1.11.2 版本之前，LZ4DecompressorWithLength 类在使用 getDecompressedLength 方法获取解压缩长度后，会无条件信任其读取的四个字节头中的“解压缩数据长度”字段，随后才对压缩输入数据进行验证。这使得攻击者只需提供长度为五个字节的恶意输入（其中四个字节头部声明一个极大的输出尺寸），即可要求分配高达约 2 GiB 的内存，从而耗尽 JVM 堆空间。 依赖于 LZ4FastDecompressor

CVSS 5.3 · Medium

Possible ATT&CK Techniques 1 AI

T1496 · Resource Hijacking
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-106453

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
yawkat LZ4 Java: LZ4DecompressorWithLength allocates the unvalidated size from the 4-byte length header, so a 5-byte input triggers a 1 GiB allocation and OutOfMemoryError
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Source: CVE Program / CVE List V5
Vulnerability Type
未经控制的内存分配
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
yawkat lz4-java < 1.11.2 -

II. Public POCs for CVE-2026-106453

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-106453

请登录查看更多情报信息。

Other References for CVE-2026-106453 (3)

Same Patch Batch · yawkat · 2026-10-06 · 5 CVEs total

CVE-2026-106451 7.3 HIGH yawkat LZ4 Java: Native library extraction to a shared temporary directory is vulnerable t
CVE-2026-106452 5.3 MEDIUM yawkat LZ4 Java: LZ4BlockInputStream allocates an unvalidated compressed length from the s
CVE-2026-106450 5.3 MEDIUM yawkat LZ4 Java: LZ4FrameInputStream reallocates block buffers for every frame, allowing C
CVE-2026-106449 3.7 LOW yawkat LZ4 Java: LZ4BlockInputStream with stopOnEmptyBlock=false recurses once per empty b

IV. Related Vulnerabilities

Same product: lz4-java
Same vendor: yawkat
Same weakness: CWE-789

V. Comments for CVE-2026-106453

No comments yet

Leave a comment