CVE-2026-108104

Xerial snappy-java 1.1.7.4 before 1.1.10.10 Double Release of Pooled Buffers in SnappyFramedInputStream

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

Analysis

AI-generated

Technical impact

The flaw is a double release of pooled buffers within SnappyFramedInputStream. When an allocation for a new buffer fails, the existing buffer is returned twice, allowing additional data to be written into the same memory region. An attacker can craft Snappy-compressed data with a large declared chunk length that triggers an OutOfMemoryError and forces this double release. The result is that the backing array of a decompressed frame may become shared among different stream instances, leading to overwritten or exposed decompressed data.

Affected Systems

The vulnerability affects the Xerial snappy-java library in any distribution that uses version 1.1.7.4 through 1.1.10.9 inclusive. Any Java application that relies on SnappyFramedInputStream for decoding Snappy frames is susceptible unless updated to 1.1.10.10 or later.

Risk and Exploitability

With a CVSS score of 6.3, the vulnerability is considered medium severity. The exploit is achievable without special privileges by sending crafted Snappy content to any component that performs framed decompression. Although the EPSS score is below 1%, indicating a very low probability of exploitation, there are no industrial exploitation reports and the vulnerability is not listed in CISA’s KEV catalog, the likelihood of exploitation remains moderate due to the widespread use of snappy‑java and the simplicity of the attack vector.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the Xerial snappy-java library to version 1.1.10.10 or later, which removes the double-release bug.
  • If an upgrade is not immediately possible, restrict the size of Snappy frames processed and reject frames that exceed a safe threshold to prevent allocation failures from triggering the double release.
  • Configure monitoring to detect repeated OutOfMemoryError messages or anomalous memory usage around snappy decompression, and investigate any suspicious activity for potential exploitation.

Generated by OpenCVE AI on October 13, 2026 at 02:11 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
Description 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.
Title Xerial snappy-java 1.1.7.4 before 1.1.10.10 Double Release of Pooled Buffers in SnappyFramedInputStream
First Time appeared Xerial
Xerial snappy-java
Weaknesses CWE-415
CPEs cpe:2.3:a:xerial:snappy-java:*:*:*:*:*:*:*:*
Vendors & Products Xerial
Xerial snappy-java
References
Metrics cvssV3_1

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

cvssV4_0

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

Weaknesses
  • CWE-1341

    Multiple Releases of Same Resource or Handle

  • CWE-415

    Double Free

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 14, 2026, 4:04 PM
Reserved
Oct 9, 2026, 1:43 PM
Status
Awaiting Analysis
Published
Oct 9, 2026, 3:17 PM
Modified
Oct 14, 2026, 5:18 PM
Severity
Moderate
Public date
Oct 9, 2026, 2:33 PM