Double Free Affecting org.xerial.snappy:snappy-java package, versions [,1.1.10.10)


Severity

Recommended
0.0
medium
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.22% (11th percentile)

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-20825056
  • published11 Oct 2026
  • disclosed9 Oct 2026
  • creditAugust829

Introduced: 9 Oct 2026

NewCVE-2026-108104  (opens in a new tab)
CWE-415  (opens in a new tab)

How to fix?

Upgrade org.xerial.snappy:snappy-java to version 1.1.10.10 or higher.

Overview

Affected versions of this package are vulnerable to Double Free via SnappyFramedInputStream in src/main/java/org/xerial/snappy/SnappyFramedInputStream.java. An attacker can make two SnappyFramedInputStream instances share the same backing array by supplying framed data with a large declared chunk length that triggers an allocation failure during buffer growth. When the stream returns its current direct and array buffers to the pool and the replacement allocation fails, close() can release the same buffers again. In deployments using the default caching buffer pool, a later stream may receive that reused buffer and read or overwrite another stream’s decompressed data.

Workarounds

  • Discard the buffer pool after an OutOfMemoryError during decompression, so the same released buffers are not reused by later SnappyFramedInputStream instances.
  • Pass a non-caching BufferPool to SnappyFramedInputStream, so buffers are not retained and handed out again to another stream after a failed allocation.

CVSS Base Scores

version 4.0
version 3.1