Skip to content
Fencer Intel
low 3.7

CVE-2026-106449 json

yawkat LZ4 Java: LZ4BlockInputStream with stopOnEmptyBlock=false recurses once per empty block, causing StackOverflowError

published last mo. modified last mo. also GHSA-343h-94h5-c4wr , EUVD-2026-93862

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

Summary

yawkat LZ4 Java provides LZ4 compression for Java. Prior to 1.11.4, net.jpountz.lz4.LZ4BlockInputStream configured with stopOnEmptyBlock set to false handles each well-formed empty LZ4Block by recursively calling refill(), allowing a long sequence of empty blocks in an attacker-controlled compressed stream to exhaust the decoding thread's stack and throw StackOverflowError. The default stopOnEmptyBlock setting is true and is not affected, and the issue does not cause memory corruption. This issue is fixed in version 1.11.4.

Patch / fix

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

Is CVE-2026-106449 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-106449 updated cvss 3.7

org.lz4/lz4-java: lz4-java: Denial of Service via stack exhaustion from empty blocks

  • Red Hat build of Apache Camel for Spring Boot 4 lz4-java 1.8.0.redhat-00010 Red Hat build of Debezium 3 lz4-java 1.8.0.redhat-00010 Red Hat Enterprise Linux 9 jmc
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Fuse 7 lz4-java 1.8.0.redhat-00010
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat JBoss Enterprise Application Platform 8 lz4-java 1.8.0.redhat-00010 Red Hat JBoss Enterprise Application Platform Expansion Pack lz4-java 1.8.0.redhat-00010 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-rocm64-torch291-py312-rhel9, rhoai/odh-th06-cuda130-torch210-py312-rhel9
    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
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

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

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
GitHub 3.1 3.7 CVSS:3.1/AV:N/AC:H/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

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.