CVE-2026-108106: Xerial snappy-java unbounded memory allocation

CVE-2026-108106 · Severity: high · CVSS 7.5 · Published 2026-10-09

Xerial snappy-java is a Java library for compressing and decompressing data using the Snappy algorithm. An unbounded memory allocation vulnerability in versions before 1.1.10.9 allows attackers to supply crafted compressed data that forces the library to allocate up to 2 GB of memory, exhausting the JVM heap and causing a denial of service. Applications that process untrusted compressed input are at risk of crashes and unavailability.

Technologies: org.xerial.snappy:snappy-java (Maven), Xerial Snappy-Java. Vendors: Maven, Xerial.

Quick answers

Is CVE-2026-108106 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-108106 being exploited in the wild.
How severe is CVE-2026-108106?
High severity, with a CVSS score of 7.5, published 9 October 2026.
Which products and versions are affected?
org.xerial.snappy:snappy-java (Maven) <= 1.1.10.8, ECOSYSTEM:introduced=0,fixed=1.1.10.9; Xerial Snappy-Java before 1.1.10.9.
Is there a fix for CVE-2026-108106?
Yes. org.xerial.snappy:snappy-java (Maven): upgrade to 1.1.10.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-108106 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-108106?
Check whether you run org.xerial.snappy:snappy-java (Maven) or 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

  • org.xerial.snappy:snappy-java (Maven): upgrade to 1.1.10.9 or later
    # set org.xerial.snappy:snappy-java to 1.1.10.9 in your pom.xml or build.gradle

Technical details

The vulnerability exists in Snappy.uncompress, uncompressString, SnappyInputStream, and SnappyFramedInputStream methods, which fail to validate the uncompressed length field in compressed input before allocating memory. An attacker can craft a few bytes of malicious compressed data with a large declared uncompressed length to trigger allocation attempts up to 2 GB, causing OutOfMemoryError and process termination. The fix is available in version 1.1.10.9 and later.

Affected products

  • Xerial snappy-java before 1.1.10.9

Identifiers

  • CVE-2026-108106
  • GHSA-q233-g92q-qxp6

Timeline

  • 2026-10-09: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.