Skip to content

CVE-2026-108106 CVE-2026-93451 CVE-2026-116590 snappy-java: unbounded allocation, heap buffer overflow and JVM crash on crafted input in cassandra-embedded (1.1.10.5 -> 1.1.10.9) - #384

Merged
vharseko merged 1 commit into
masterfrom
dependabot/maven/cassandra-embedded/org.xerial.snappy-snappy-java-1.1.10.9
Nov 1, 2026
Merged

vharseko merged 1 commit into
masterfrom
dependabot/maven/cassandra-embedded/org.xerial.snappy-snappy-java-1.1.10.9

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 29, 2026 •

Copy link
Copy Markdown
Contributor

Bumps org.xerial.snappy:snappy-java from 1.1.10.5 to 1.1.10.9 in cassandra-embedded/pom.xml, clearing Dependabot alerts #117, #118 and #119.

Advisories

All three affect org.xerial.snappy:snappy-java <= 1.1.10.8 and are fixed in 1.1.10.9.

CVE-2026-108106 / GHSA-q233-g92q-qxp6: unbounded memory allocation from an attacker-declared uncompressed length

Several decompression paths size the output buffer from the uncompressed length declared in the first bytes of the compressed data, before decompressing or validating it. A few bytes of crafted input force an allocation of up to 2 GB (OutOfMemoryError), or a NegativeArraySizeException for declared lengths of 2^31 or more. Affected entry points are 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. In 1.1.10.9, Snappy.uncompressedLength() rejects negative lengths and lengths above 64/3 of the compressed size, which is the densest expansion Snappy can encode (xerial/snappy-java@943c604).

Severity High, CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
Weakness CWE-770, CWE-789
Alert #117

CVE-2026-93451 / GHSA-gwq9-9ffj-mvrv: heap buffer overflow in the Snappy.uncompress*Array typed-array methods

uncompressCharArray, uncompressShortArray, uncompressIntArray, uncompressLongArray, uncompressFloatArray and uncompressDoubleArray size the result array as the declared byte length divided by the element size, but the native code writes the full byte length. When that length is not a multiple of the element size, up to 7 bytes are written past the end of the Java array and corrupt the heap. 1.1.10.9 rejects such lengths with SnappyIOException (xerial/snappy-java@943c604).

Severity High, CVSS 3.1 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)
Weakness CWE-193, CWE-787
Alert #119

CVE-2026-116590 / GHSA-xqrx-qh46-34m7: JVM crash from unchecked ranges in Snappy.arrayCopy and SnappyOutputStream.rawWrite

Snappy.arrayCopy(Object, int, int, Object, int) calls a native memcpy without validating the ranges, so a negative or oversized length or offset reads or writes outside the arrays and crashes the JVM. SnappyOutputStream.rawWrite and SnappyInputStream.rawRead pass caller-supplied ranges to it, and so do the typed-array write/read methods built on them. In 1.1.10.9, arrayCopy checks both ranges before copying, the stream methods validate offsets and lengths, and typed-array ranges whose byte size overflows int are rejected (xerial/snappy-java@2d7ca71).

Severity Medium, CVSS 3.1 5.9 (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H)
Weakness CWE-129, CWE-787
Alert #118

Impact on commons

Low. No commons code calls snappy-java. cassandra-embedded declares it only to pin a newer version than the 1.1.10.4 that cassandra-all 5.0.7 manages, and the embedded Cassandra server is its only user. Cassandra 5.0.7 calls Snappy in two places:

  • org.apache.cassandra.transport.Compressor.SnappyCompressor compresses CQL frames when a client asks for snappy in STARTUP, on native protocol v4 and earlier. The embedded cassandra.yaml keeps native_transport_allow_older_protocols: true. This is the only path that takes remote input, and a client can reach it before authenticating. decompress first rejects the frame with a ProtocolException unless Snappy.isValidCompressedBuffer accepts it. That check walks the whole stream without writing output and requires the produced length to equal the declared one. Only after it passes does decompress size the buffer with Snappy.uncompressedLength(input) and call Snappy.uncompress(byte[], int, int, byte[], int). A frame that declares gigabytes in a few bytes, the CVE-2026-108106 case, is therefore already rejected on 1.1.10.5. The allocation is bounded by what the frame really expands to, the same bound 1.1.10.9 introduces.
  • org.apache.cassandra.io.compress.SnappyCompressor handles SSTable compression. It is used only by a table created with SnappyCompressor; the default is LZ4, and commit-log and hints compression are left commented out in the embedded cassandra.yaml. It decompresses local files with Snappy.rawUncompress and Snappy.uncompress(ByteBuffer, ByteBuffer) into buffers Cassandra sizes itself.

Neither path uses the typed-array methods (CVE-2026-93451), Snappy.arrayCopy or the Snappy streams (CVE-2026-116590). None of the three advisories therefore has a reachable path in the embedded server as configured. The dependency has compile scope, so projects that depend on the published cassandra-embedded artifact resolve the version it pins. The bump takes that version out of the vulnerable range.

Change

org.xerial.snappy:snappy-java goes from 1.1.10.5 to 1.1.10.9 in cassandra-embedded/pom.xml; there is no code change. The new length checks reject only input that cannot be valid Snappy data, so valid CQL frames and SSTables decompress as before.

References

Bumps [org.xerial.snappy:snappy-java](https://github.com/xerial/snappy-java) from 1.1.10.5 to 1.1.10.9.
- [Release notes](https://github.com/xerial/snappy-java/releases)
- [Commits](xerial/snappy-java@v1.1.10.5...v1.1.10.9)

---
updated-dependencies:
- dependency-name: org.xerial.snappy:snappy-java
  dependency-version: 1.1.10.9
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file java Pull requests that update java code labels Oct 29, 2026
@vharseko vharseko added the security Security fixes and CVE remediation label Oct 29, 2026
@vharseko vharseko changed the title Bump org.xerial.snappy:snappy-java from 1.1.10.5 to 1.1.10.9 in /cassandra-embedded CVE-2026-108106 CVE-2026-93451 CVE-2026-116590 snappy-java: unbounded allocation, heap buffer overflow and JVM crash on crafted input in cassandra-embedded (1.1.10.5 -> 1.1.10.9) Oct 29, 2026
@vharseko
vharseko merged commit 5e12aa5 into master Nov 1, 2026
14 checks passed
@vharseko
vharseko deleted the dependabot/maven/cassandra-embedded/org.xerial.snappy-snappy-java-1.1.10.9 branch November 1, 2026 13:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file java Pull requests that update java code security Security fixes and CVE remediation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant