Memory Allocation with Excessive Size Value Affecting org.xerial.snappy:snappy-java package, versions [,1.1.10.9)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGXERIALSNAPPY-20825055
- published11 Oct 2026
- disclosed9 Oct 2026
- credit1seal, EndlssNightmare, taer, August829, apvxlab, trnguyencflt
Introduced: 9 Oct 2026
NewCVE-2026-108106 (opens in a new tab)How to fix?
Upgrade org.xerial.snappy:snappy-java to version 1.1.10.9 or higher.
Overview
Affected versions of this package are vulnerable to Memory Allocation with Excessive Size Value through the Snappy.uncompressedLength and decompression paths in Snappy.java and SnappyFramedInputStream. An attacker can exhaust JVM memory by supplying a crafted compressed payload that advertises a huge uncompressed size, causing Snappy.uncompress, Snappy.uncompressString, array decompression helpers, or framed stream decompression to allocate an oversized output buffer before validating the length. This can trigger OutOfMemoryError or a NegativeArraySizeException from only a few bytes of attacker-controlled input. The result is denial of service for applications that accept untrusted Snappy-compressed data.
Workarounds
- Before decompressing untrusted data, call
Snappy.uncompressedLength(input)and reject inputs whose declared uncompressed length exceeds an application-specific maximum; this prevents attacker-supplied payloads from forcing oversized JVM allocations during Snappy decompression.