cve.bz

CVE-2026-106449 yawkat lz4-java: Uncontrolled Recursion

3.7 lowEPSS 0.4%Fix available

Low (3.7) in yawkat lz4-java. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in at.yawk.lz4:lz4-java 1.11.4.

On this page
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.

Severity

CVSS 3.1

3.7 low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-07. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-674 Uncontrolled Recursion
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • at.yawk.lz4:lz4-java (Maven): fixed in 1.11.4

Ask an AI about this CVE

Show the promptExplain CVE-2026-106449 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106449?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106449?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106449 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
yawkat lz4-java< 1.11.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-343h-94h5-c4wrMavenat.yawk.lz4:lz4-java<1.11.41.11.4
GHSA-343h-94h5-c4wrMavenorg.lz4:lz4-java<=1.8.1no fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14lz4-javano fix listedDEBIAN-CVE-2026-106449
Ubuntu20.04:LTS, 22.04:LTS, 24.04:LTS and 2 morelz4-javano fix listedUBUNTU-CVE-2026-106449

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Low.

Red Hat's statement

This vulnerability is rated with a Low severity impact on Red Hat products because triggering the condition depends on non-default stream configuration parameters and the resulting impact is confined to a denial of service via thread stack exhaustion. Standard deployments utilize default decoding options that halt upon encountering zero-length blocks, inherently preventing recursive processing of malicious inputs. Furthermore, even when improperly configured, processing malformed streams causes a localized thread crash without leading to privilege escalation, arbitrary code execution, or memory corruption.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat build of Apache Camel for Spring Boot 4lz4-javaFix deferred
Red Hat build of Debezium 3lz4-javaFix deferred
Red Hat Enterprise Linux 9jmcFix deferred
Red Hat Fuse 7lz4-javaOut of support scope
Red Hat JBoss Enterprise Application Platform 8lz4-javaFix deferred
Red Hat JBoss Enterprise Application Platform Expansion Packlz4-javaFix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-spark-operator-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cpu-torch210-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cuda130-torch210-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-rocm64-torch291-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th-torch-cpu-py312-rhel9Fix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-th-torch-cuda-py312-rhel9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-106449.

Attack patterns (CAPEC)

  • CAPEC-230 Serialized Data with Nested Payloads Likelihood: Medium · Severity: High
  • CAPEC-231 Oversized Serialized Data Payloads Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON