HighGHSA-q233-g92q-qxp6CVE-2026-108106

snappy-java: Unbounded memory allocation from attacker-declared uncompressed lengtha

Published 27 Oct 2026 · Updated 27 Oct 2026

Is your project on an affected org.xerial.snappy:snappy-java?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<1.1.10.9
Fixed in
1.1.10.9
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.xerial.snappy:snappy-java -DdepVersion=1.1.10.9 -DforceVersion=true

Details

Impact

Several decompression paths in snappy-java allocate an output buffer sized by the uncompressed length declared in the first bytes of the compressed data, before decompressing or validating it. A few bytes of crafted input can therefore force an allocation of up to 2 GB, causing OutOfMemoryError (denial of service), or a NegativeArraySizeException for declared lengths of 2^31 or more.

Affected entry points include Snappy.uncompress(byte[]), Snappy.uncompressString, the Snappy.uncompress*Array methods, SnappyInputStream, and SnappyFramedInputStream. The maxChunkSize limit added for CVE-2023-43642 bounds only the compressed chunk length, so it does not prevent this.

Patches

Fixed in 1.1.10.9 (#739). Snappy.uncompressedLength() now rejects negative declared lengths, and lengths larger than any valid Snappy stream of the given size can produce. The densest Snappy element expands 3 bytes to 64, so the limit is 64/3 of the compressed size. Allocations are therefore proportional to the input actually received.

Workarounds

Before decompressing untrusted data, check that Snappy.uncompressedLength(input) is within an application-specific limit.

Is GHSA-q233-g92q-qxp6 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.xerial.snappy:snappy-java, and gives you the command that fixes it.

More advisories for org.xerial.snappy:snappy-java

  • HighCVE-2026-93451snappy-java: Heap buffer overflow in Snappy.uncompress*Array typed-array methods · 27 Oct 2026
  • MediumCVE-2026-116590snappy-java: JVM crash from unchecked ranges in Snappy.arrayCopy and SnappyOutputStream.rawWrite · 27 Oct 2026
  • HighCVE-2023-43642snappy-java's missing upper bound check on chunk length can lead to Denial of Service (DoS) impact · 25 Sept 2023
  • HighCVE-2023-34455snappy-java's unchecked chunk length leads to DoS · 15 Jun 2023
  • MediumCVE-2023-34454snappy-java's Integer Overflow vulnerability in compress leads to DoS · 15 Jun 2023
  • MediumCVE-2023-34453snappy-java's Integer Overflow vulnerability in shuffle leads to DoS · 15 Jun 2023
org.xerial.snappy:snappy-java security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.