CVE-2026-108106Xerial snappy-java before 1.1.10.9 Unbounded Memory Allocation Denial of Service
Updated under an hour ago ()
Does this affect you?
It affects xerial snappy-java. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.37%, higher than 30% of scored CVEs.
Do this next
Free account, 1 product
Xerial snappy-java before 1.1.10.9 contains an unbounded memory allocation vulnerability that allows attackers to exhaust JVM memory by declaring a large uncompressed length in compressed input. Attackers can supply a few crafted bytes to Snappy.uncompress, uncompressString, SnappyInputStream or SnappyFramedInputStream to force allocations up to 2 GB, causing OutOfMemoryError and denial of service.
- CVSS
- 7.5 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- CWE-789
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.37% (percentile 30)
- Assigned by
- VulnCheck
- NVD analysis
- Awaiting Analysis
- Record last updated
- Oct 13, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
xerial snappy-java xerial:snappy_java (from the name) | before 1.1.10.9; 1.1.10.9 not affected | CNA record |
References
- https://github.com/xerial/snappy-java/security/advisories/GHSA-q233-g92q-qxp6vendor-advisory
- https://github.com/xerial/snappy-java/commit/943c6043a292568575e8347af4507d015e802c75patch
- https://github.com/xerial/snappy-java/releases/tag/v1.1.10.9release-notes
- https://github.com/xerial/snappy-java/blob/v1.1.10.8/src/main/java/org/xerial/snappy/Snappy.java#L517technical-description
- https://github.com/xerial/snappy-javaproduct
- https://www.vulncheck.com/advisories/xerial-snappy-java-before-1.1.10.9-unbounded-memory-allocation-denial-of-servicethird-party-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.