Repository navigation
Conversation
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>
vharseko
deleted the
dependabot/maven/cassandra-embedded/org.xerial.snappy-snappy-java-1.1.10.9
branch
November 1, 2026 13:00
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps
org.xerial.snappy:snappy-javafrom 1.1.10.5 to 1.1.10.9 incassandra-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 aNegativeArraySizeExceptionfor declared lengths of 2^31 or more. Affected entry points areSnappy.uncompress(byte[]),Snappy.uncompressString, theSnappy.uncompress*Arraymethods,SnappyInputStreamandSnappyFramedInputStream. ThemaxChunkSizelimit 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).AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)CVE-2026-93451 / GHSA-gwq9-9ffj-mvrv: heap buffer overflow in the
Snappy.uncompress*Arraytyped-array methodsuncompressCharArray,uncompressShortArray,uncompressIntArray,uncompressLongArray,uncompressFloatArrayanduncompressDoubleArraysize 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 withSnappyIOException(xerial/snappy-java@943c604).AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H)CVE-2026-116590 / GHSA-xqrx-qh46-34m7: JVM crash from unchecked ranges in
Snappy.arrayCopyandSnappyOutputStream.rawWriteSnappy.arrayCopy(Object, int, int, Object, int)calls a nativememcpywithout validating the ranges, so a negative or oversized length or offset reads or writes outside the arrays and crashes the JVM.SnappyOutputStream.rawWriteandSnappyInputStream.rawReadpass caller-supplied ranges to it, and so do the typed-arraywrite/readmethods built on them. In 1.1.10.9,arrayCopychecks both ranges before copying, the stream methods validate offsets and lengths, and typed-array ranges whose byte size overflowsintare rejected (xerial/snappy-java@2d7ca71).AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H)Impact on commons
Low. No commons code calls snappy-java.
cassandra-embeddeddeclares it only to pin a newer version than the 1.1.10.4 thatcassandra-all5.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.SnappyCompressorcompresses CQL frames when a client asks forsnappyinSTARTUP, on native protocol v4 and earlier. The embeddedcassandra.yamlkeepsnative_transport_allow_older_protocols: true. This is the only path that takes remote input, and a client can reach it before authenticating.decompressfirst rejects the frame with aProtocolExceptionunlessSnappy.isValidCompressedBufferaccepts it. That check walks the whole stream without writing output and requires the produced length to equal the declared one. Only after it passes doesdecompresssize the buffer withSnappy.uncompressedLength(input)and callSnappy.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.SnappyCompressorhandles SSTable compression. It is used only by a table created withSnappyCompressor; the default is LZ4, and commit-log and hints compression are left commented out in the embeddedcassandra.yaml. It decompresses local files withSnappy.rawUncompressandSnappy.uncompress(ByteBuffer, ByteBuffer)into buffers Cassandra sizes itself.Neither path uses the typed-array methods (CVE-2026-93451),
Snappy.arrayCopyor 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 publishedcassandra-embeddedartifact resolve the version it pins. The bump takes that version out of the vulnerable range.Change
org.xerial.snappy:snappy-javagoes from1.1.10.5to1.1.10.9incassandra-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