CVE-2026-108106

Xerial snappy-java before 1.1.10.9 Unbounded Memory Allocation Denial of Service

Published Oct 9, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability is an unbounded memory allocation in Xerial snappy-java that occurs when the library uncompresses data. A crafted input can declare an extremely large uncompressed length, causing Snappy.uncompress, Snappy.uncompressString, or the stream classes to allocate up to 2 GB of RAM. This triggers an OutOfMemoryError, which aborts the Java Virtual Machine and results in denial of service to any running application. The weakness is a classic over‑allocating flaw and maps to CWE‑770 (Uncontrolled Resource Consumption) and CWE‑789 (Uncontrolled Memory Allocation).

Affected Systems

Affected versions of the library start with the upstream release v1.1.10.9; any installation of xerial snappy-java older than 1.1.10.9, such as 1.1.10.8 and earlier, is vulnerable. The issue applies to all builds that use the default uncompress implementations in the public API.

Risk and Exploitability

The CVSS score of 8.7 indicates high severity. The EPSS score is not available, suggesting limited public exploitation data, and the vulnerability is not listed in CISA’s KEV catalog. Attackers can trigger the flaw by providing malicious compressed data; if the functions are invoked on data received from a remote client, the attack vector is inferred to be remote, otherwise the vector remains local. Exploitation forces a 2 GB allocation, causing the process to terminate and denying service to dependent components.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to snappy-java 1.1.10.9 or later.
  • If an upgrade is delayed, validate the size of compressed input before passing it to the uncompress functions.
  • Configure a JVM heap limit or sandbox environment to prevent large allocations from crashing the process.

Generated by OpenCVE AI on October 10, 2026 at 02:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-q233-g92q-qxp6 snappy-java: Unbounded memory allocation from attacker-declared uncompressed lengtha
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description 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.
Title Xerial snappy-java before 1.1.10.9 Unbounded Memory Allocation Denial of Service
First Time appeared Xerial
Xerial snappy-java
Weaknesses CWE-789
CPEs cpe:2.3:a:xerial:snappy-java:*:*:*:*:*:*:*:*
Vendors & Products Xerial
Xerial snappy-java
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-770

    Allocation of Resources Without Limits or Throttling

  • CWE-789

    Memory Allocation with Excessive Size Value

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 13, 2026, 4:51 PM
Reserved
Oct 9, 2026, 1:44 PM
Status
Awaiting Analysis
Published
Oct 9, 2026, 3:17 PM
Modified
Oct 13, 2026, 5:17 PM
Severity
Important
Public date
Oct 9, 2026, 2:33 PM