https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 08 Oct 2026 19:36:26 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-106449 <p>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&#39;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.</p> <p>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&#39;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.</p> https://db.gcve.eu/vuln/fkie_cve-2026-106449 https://db.gcve.eu/vuln/ghsa-343h-94h5-c4wr <p><strong>Affected:</strong> Maven: at.yawk.lz4:lz4-java, Maven: org.lz4:lz4-java</p> <p>### Summary</p> <p>When `LZ4BlockInputStream` is configured with `stopOnEmptyBlock = false` (the mode for reading concatenated block streams), it handles each empty block by calling `refill()` recursively. A long run of empty blocks exhausts the thread stack and throws `StackOverflowError` out of `read()` or `skip()`.</p> <p>### Details</p> <p>In `net.jpountz.lz4.LZ4BlockInputStream.refill()`:</p> <p>```java if (originalLen == 0 &amp;&amp; compressedLen == 0) { if (check != 0) { throw new IOException(&#34;Stream is corrupted&#34;); } if (!stopOnEmptyBlock) { refill(); } else { finished = true; } return; } ```</p> <p>Each well-formed empty block is 21 bytes and adds one stack frame, with no limit on nesting depth. In local testing, around 10,000 to 100,000 consecutive empty blocks (about 210 KB to 2.1 MB, depending on JIT state and thread stack size) threw `StackOverflowError`. `StackOverflowError` is an `Error`, not an `IOException`, so callers that only handle I/O errors for corrupt input don&#39;t catch it.</p> <p>### Impact</p> <p>Applications that decode attacker-controlled `LZ4Block` streams with `LZ4BlockInputStream.newBuilder().withStopOnEmptyBlock(false)` or the deprecated `LZ4BlockInputStream(InputStream, boolean)` constructor can have the decoding thread fail with `StackOverflowError`. The default configuration (`stopOnEmptyBlock = true`) is not affected. There is no memory corruption. Availability impact only.</p> <p>### Patch</p> <p>Fixed in lz4-java 1.11.4. Empty blocks are now skipped in a loop instead of by r…</p> <p><strong>Affected:</strong> Maven: at.yawk.lz4:lz4-java, Maven: org.lz4:lz4-java</p> <p>### Summary</p> <p>When `LZ4BlockInputStream` is configured with `stopOnEmptyBlock = false` (the mode for reading concatenated block streams), it handles each empty block by calling `refill()` recursively. A long run of empty blocks exhausts the thread stack and throws `StackOverflowError` out of `read()` or `skip()`.</p> <p>### Details</p> <p>In `net.jpountz.lz4.LZ4BlockInputStream.refill()`:</p> <p>```java if (originalLen == 0 &amp;&amp; compressedLen == 0) { if (check != 0) { throw new IOException(&#34;Stream is corrupted&#34;); } if (!stopOnEmptyBlock) { refill(); } else { finished = true; } return; } ```</p> <p>Each well-formed empty block is 21 bytes and adds one stack frame, with no limit on nesting depth. In local testing, around 10,000 to 100,000 consecutive empty blocks (about 210 KB to 2.1 MB, depending on JIT state and thread stack size) threw `StackOverflowError`. `StackOverflowError` is an `Error`, not an `IOException`, so callers that only handle I/O errors for corrupt input don&#39;t catch it.</p> <p>### Impact</p> <p>Applications that decode attacker-controlled `LZ4Block` streams with `LZ4BlockInputStream.newBuilder().withStopOnEmptyBlock(false)` or the deprecated `LZ4BlockInputStream(InputStream, boolean)` constructor can have the decoding thread fail with `StackOverflowError`. The default configuration (`stopOnEmptyBlock = true`) is not affected. There is no memory corruption. Availability impact only.</p> <p>### Patch</p> <p>Fixed in lz4-java 1.11.4. Empty blocks are now skipped in a loop instead of by r…</p> https://db.gcve.eu/vuln/ghsa-343h-94h5-c4wr https://db.gcve.eu/vuln/ubuntu-cve-2026-106449 <p><strong>Affected:</strong> Ubuntu:20.04:LTS: lz4-java, Ubuntu:22.04:LTS: lz4-java, Ubuntu:24.04:LTS: lz4-java, Ubuntu:26.04:LTS: lz4-java</p> <p>(yawkat LZ4 Java provides LZ4 compression for Java. Prior to 1.11.4, ne ...)</p> <p><strong>Affected:</strong> Ubuntu:20.04:LTS: lz4-java, Ubuntu:22.04:LTS: lz4-java, Ubuntu:24.04:LTS: lz4-java, Ubuntu:26.04:LTS: lz4-java</p> <p>(yawkat LZ4 Java provides LZ4 compression for Java. Prior to 1.11.4, ne ...)</p> https://db.gcve.eu/vuln/ubuntu-cve-2026-106449