Skip to content
Fencer Intel
medium 5.3

CVE-2026-106450 json

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

published last mo. modified last mo. also GHSA-gm45-99xc-r7wv , EUVD-2026-93865

cvss
5.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 39%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven at.yawk.lz4:lz4-java 1.11.4

Is CVE-2026-106450 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-106450 updated cvss 5.3

org.lz4/lz4-java: lz4-java: Denial of Service via excessive memory allocation from crafted compressed streams

  • Red Hat OpenShift Developer Tools and Services jenkins-2-plugins, ocp-tools-4/jenkins-rhel8, ocp-tools-4/jenkins-rhel9 Red Hat build of Apache Camel 4 for Quarkus 3 lz4-java Red Hat build of Apache Camel for Spring Boot 4 lz4-java, liblz4-java.so Red Hat build of Apicurio Registry 3 lz4-java Red Hat build of Debezium 3 lz4-java
    affected: workaround, no fix available “Fix deferred”
  • Red Hat build of Quarkus lz4-java
    affected: workaround, no fix available
  • Red Hat Enterprise Linux 8 lz4-java, lz4-java-javadoc Red Hat Enterprise Linux 9 jmc
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Fuse 7 lz4-java
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat Hardened Images maven3.9 Red Hat JBoss Enterprise Application Platform 8 lz4-java, liblz4-java.so Red Hat JBoss Enterprise Application Platform Expansion Pack lz4-java, liblz4-java.so Red Hat OpenShift AI (RHOAI) rhoai/odh-spark-operator-rhel9, rhoai/odh-th-torch-cpu-py312-rhel9, rhoai/odh-th-torch-cuda-py312-rhel9, rhoai/odh-th06-cpu-torch210-py312-rhel9, rhoai/odh-th06-cpu-torch291-py312-rhel9, rhoai/odh-th06-rocm64-torch291-py312-rhel9, +2 more
    affected: workaround, no fix available “Fix deferred”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
GitHub 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
maven at.yawk.lz4:lz4-java
<1.11.4
1.11.4
maven org.lz4:lz4-java
<=1.8.1
 no fix listed

Affected products

  • yawkat lz4-java

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.