CVE-2026-108104
MediumCVSS 4.8Summary
Xerial snappy-java from 1.1.7.4 before 1.1.10.10 contains a double release vulnerability in SnappyFramedInputStream that returns pooled buffers twice when replacement allocation fails. Attackers can supply framed data with a large declared chunk length to trigger OutOfMemoryError, causing shared backing arrays that expose or overwrite other streams' decompressed data.
Risk Assessment
An attacker can trigger an out-of-memory error and cause exposure or overwriting of other streams' data, leading to information disclosure or data corruption.
Recommendation
Update snappy-java to version 1.1.10.10 or later.
Other vulnerabilities in snappy-java
See all- CVE-2026-108106High
Xerial snappy-java before 1.1.10.9 contains an unbounded memory allocation vulnerability that allows attackers to exhaust JVM memory by declaring a large uncompressed length in compressed input. Attackers can supply a few crafted bytes to Snappy.uncompress, uncompressString, SnappyInputStream or SnappyFramedInputStream to force allocations up to 2 GB, causing OutOfMemoryError and denial of service.
- CVE-2026-93452High
snappy-java through 1.1.10.8 contains a buffer overflow vulnerability in Snappy.compress(ByteBuffer, ByteBuffer) that writes past the end of the destination buffer. Attackers can supply incompressible data that exceeds the destination buffer's remaining capacity, corrupting off-heap memory and causing JVM termination.
- CVE-2026-93451Medium
snappy-java through 1.1.10.8 contains a buffer overflow vulnerability in typed Snappy.uncompress*Array methods that allocate output arrays by dividing uncompressed length by element size but pass the undivided length to native code. Attackers controlling compressed input can cause misaligned length values to write past array bounds with attacker-controlled bytes, corrupting heap memory.
- CVE-2026-90559High
snappy-java through 1.1.10.8 contains an out-of-bounds write vulnerability in Snappy.uncompress(ByteBuffer, ByteBuffer) because destination buffer capacity is never validated against decompressed size. Attackers can supply valid compressed data that decompresses larger than the destination buffer, causing writes past buffer boundaries and JVM termination.
- CVE-2023-34455High
The snappy-java library has a flaw related to unchecked chunk length that can lead to a critical error in versions prior to 1.1.10.1. The hasNextChunk function does not validate the chunkSize variable, which can result in a NegativeArraySizeException or OutOfMemoryError.
- CVE-2023-34454Medium
The snappy-java library has an issue with unchecked multiplications that may lead to integer overflow in versions prior to 1.1.10.1. The `compress(char[] input)` function does not check the length of the array, which can result in critical errors.
- CVE-2023-34453Medium
The snappy-java library has a vulnerability related to unchecked multiplications, which may lead to integer overflow in versions prior to 1.1.10.1. The `shuffle(int[] input)` function can cause a critical error when the array length is not properly checked.
Original NVD description (English source)
Xerial snappy-java from 1.1.7.4 before 1.1.10.10 contains a double release vulnerability in SnappyFramedInputStream that returns pooled buffers twice when replacement allocation fails. Attackers can supply framed data with a large declared chunk length to trigger OutOfMemoryError, causing shared backing arrays that expose or overwrite other streams' decompressed data.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS

