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.
CVE-2026-106449
This low-severity CVE scores 3.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
The CVE record names the fixed release — apply it.
- CVSS v3
- 3.7
- EG Score
- 3.7LOWlow confidence
- EG Risk
- 17EG Risk 17/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity37% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: The CVE record names the fixed release. Apply it within your standard update timelines. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
The CVE record names the fixed release. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 6, 2026
Last Modified
October 7, 2026
References (3)
- security-advisories@githubhttps://github.com/yawkat/lz4-java/commit/c8ebf97d504fb34434fda46fc761e8202570e0d8
- security-advisories@githubhttps://github.com/yawkat/lz4-java/releases/tag/v1.11.4
- security-advisories@githubhttps://github.com/yawkat/lz4-java/security/advisories/GHSA-343h-94h5-c4wr
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-07 17:39 UTCEG score recompute
- 2026-10-07 16:51 UTCEG score recompute
- 2026-10-06 20:32 UTCEG score recompute
- 2026-10-06 19:52 UTCEG score recompute
- 2026-10-06 19:51 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-106449?
When was CVE-2026-106449 disclosed?
What is the CVSS score of CVE-2026-106449?
How do I remediate CVE-2026-106449?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-106449
Is Your Infrastructure Affected by CVE-2026-106449?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.