CVE-2026-106450

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

Published Oct 6, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability arises when LZ4FrameInputStream allocates two 4 MiB buffers per maximum‑block‑size frame header, causing amplification. Attacker‑controlled streams full of tiny empty frames can trigger about 8 MiB of allocation for every 11 bytes of input, leading to elevated CPU and garbage‑collection activity with no decompressed data produced.

Affected Systems

The issue affects the yawkat lz4‑java library versions prior to 1.11.4. Users relying on that library, especially in environments that enable concatenated‑frame mode, are susceptible.

Risk and Exploitability

Based on the description, it is inferred that an attacker can supply a crafted stream from an untrusted or nearby source to trigger the amplification. The CVSS score is 5.3, indicating a moderate impact. With no EPSS score available and the vulnerability not listed in CISA KEV, exploitation is possible especially when concatenated‑frame mode is used. The effect is primarily denial of service via excessive CPU and memory consumption; there is no evidence of code execution or data disclosure.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to v1.11.4 or later
  • Disable concatenated‑frame mode if not required, or validate input before feeding it to LZ4FrameInputStream
  • Monitor system for abnormal CPU and GC spikes and enforce limits on data ingest

Generated by OpenCVE AI on October 7, 2026 at 01:14 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-gm45-99xc-r7wv yawkat LZ4 Java: LZ4FrameInputStream reallocates block buffers for every frame, allowing CPU and GC amplification from small inputs
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Yawkat
Yawkat lz4-java
Vendors & Products Yawkat
Yawkat lz4-java
Type Values Removed Values Added
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.
Title yawkat LZ4 Java: LZ4FrameInputStream reallocates block buffers for every frame, allowing CPU and GC amplification from small inputs
Weaknesses CWE-770
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 9, 2026, 1:44 AM
Reserved
Oct 6, 2026, 4:49 PM
Status
Awaiting Analysis
Published
Oct 6, 2026, 8:17 PM
Modified
Oct 9, 2026, 2:16 AM
Severity
Moderate
Public date
Oct 6, 2026, 7:48 PM