snappy-java: Unbounded memory allocation from attacker-declared uncompressed length
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.
What to do
Upgrade to 1.1.10.9 or later.
Workarounds
Before decompressing untrusted data, check that Snappy.uncompressedLength(input) is within an application-specific limit.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.xerial.snappy:snappy-java | < 1.1.10.9 | 1.1.10.9 |
References
- https://github.com/xerial/snappy-java/security/advisories/GHSA-q233-g92q-qxp6
- https://nvd.nist.gov/vuln/detail/CVE-2026-108106
- https://github.com/xerial/snappy-java/pull/739
- https://github.com/xerial/snappy-java/commit/943c6043a292568575e8347af4507d015e802c75
- https://github.com/xerial/snappy-java
- https://github.com/xerial/snappy-java/blob/v1.1.10.8/src/main/java/org/xerial/snappy/Snappy.java#L517
- https://github.com/xerial/snappy-java/releases/tag/v1.1.10.9
- https://www.vulncheck.com/advisories/xerial-snappy-java-before-1.1.10.9-unbounded-memory-allocation-denial-of-service
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H- Weakness (CWE)
CWE-770, CWE-789- Platform
- Java / Kotlin (Maven)
- Package
org.xerial.snappy:snappy-java- Disclosed
- 27.10.2026
- Updated
- 01.11.2026 10:00
Sources and licenses · Edited or translated by DockRay; source rights and applicable licenses are retained.
OSV / GitHub Advisory Database - GHSA-q233-g92q-qxp6 - CC BY 4.0
Vulnerability history: org.xerial.snappy:snappy-java
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 7
- First → latest
- 06.2023 10.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 4
- Medium 3
Disclosures per year
- 2023: 4
- 2024: 0
- 2025: 0
- 2026: 3
-
snappy-java: Unbounded memory allocation from attacker-declared uncompressed length this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.