# CVE-2026-108104: Xerial snappy-java double release vulnerability in SnappyFramedInputStream

Source: https://junglewise.ai/threats/cve-2026-108104-xerial-snappy-java-from-1-1-7-4-before-1-1-10-10-contains-a  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-09. Updated: 2026-10-16  
License: CC BY 4.0 with a link back

CVE-2026-108104 · Severity: medium · CVSS 4.8 · Published 2026-10-09

Xerial snappy-java is a Java library for compressing and decompressing data using the Snappy algorithm. A vulnerability in the SnappyFramedInputStream class can cause it to release pooled buffers twice, allowing an attacker to craft malicious compressed data that triggers memory exhaustion and exposes or overwrites data from other decompression streams.

Technologies: [Xerial Snappy-Java](https://junglewise.ai/threats/technologies/snappy-java). Vendors: [Xerial](https://junglewise.ai/threats/vendors/xerial).

## Quick answers

**Is CVE-2026-108104 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-108104 being exploited in the wild.

**How severe is CVE-2026-108104?** Medium severity, with a CVSS score of 4.8, published 9 October 2026.

**Which products and versions are affected?** Xerial Snappy-Java 1.1.7.4 through 1.1.10.9.

**Is there a fix for CVE-2026-108104?** Yes: fixed in 1.1.10.10. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-108104 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-108104?** Check whether you run Xerial Snappy-Java at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 1.1.10.10

## Technical details

The vulnerability is a double-release flaw in SnappyFramedInputStream where pooled buffers are returned twice when memory allocation fails during decompression. An attacker can supply framed Snappy data with a large declared chunk length to trigger an OutOfMemoryError, causing shared backing arrays to be reused across different streams, leading to data corruption or exposure. The issue affects versions 1.1.7.4 through 1.1.10.9.

## Affected products

- Xerial snappy-java 1.1.7.4 through 1.1.10.9

## Timeline

- 2026-10-09: disclosed

## References

- [https://github.com/xerial/snappy-java](https://github.com/xerial/snappy-java)
- [https://github.com/xerial/snappy-java/blob/v1.1.10.9/src/main/java/org/xerial/snappy/SnappyFramedInputStream.java](https://github.com/xerial/snappy-java/blob/v1.1.10.9/src/main/java/org/xerial/snappy/SnappyFramedInputStream.java)

## Related threats

- [snappy-java buffer overflow in arrayCopy](https://junglewise.ai/threats/cve-2026-116590-snappy-java-is-a-java-port-of-the-snappy-a-fast-c-compresser)
- [snappy-java unbounded memory allocation in decompression](https://junglewise.ai/threats/duplicate-advisory-snappy-java-unbounded-memory-allocation-from-ac3e5e8e)
- [Xerial snappy-java unbounded memory allocation](https://junglewise.ai/threats/cve-2026-108106-xerial-snappy-java-before-1-1-10-9-contains-an-unbounded-memory)
- [snappy-java buffer overflow in compress](https://junglewise.ai/threats/cve-2026-93452-snappy-java-buffer-overflow-in-compress)
- [snappy-java buffer overflow in Snappy.uncompress*Array](https://junglewise.ai/threats/cve-2026-93451-snappy-java-buffer-overflow-in-snappy-uncompress-array)