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.
CVE-2026-108106
HIGHPre-NVD 7.57.5—Trending — 3 sources updated this week
EchelonGraph scoreHIGH confidence
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-09. A secondary CVSS source baseline 7.5; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.5Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHhigh confidence
- EG Risk
- 38EG Risk 38/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 9, 2026
Last Modified
October 9, 2026
Advisory Details (6)
Auto-updated Oct 9, 2026Patch available. Sources: github, github_commit, github_release.
generic
Xerial snappy-java before 1.1.10.9 Unbounded Memory Allocation Denial of Service | Advisories | VulnCheck
https://www.vulncheck.com/advisories/xerial-snappy-java-before-1.1.10.9-unbounded-memory-allocation-denial-of-servicegeneric
GitHub - xerial/snappy-java: Snappy compressor/decompressor for Java · GitHub
https://github.com/xerial/snappy-javageneric
snappy-java/src/main/java/org/xerial/snappy/Snappy.java at v1.1.10.8 · xerial/snappy-java · GitHub
https://github.com/xerial/snappy-java/blob/v1.1.10.8/src/main/java/org/xerial/snappy/Snappy.java#L517github_release Patch Available
v1.1.10.9
Patch available: xerial/snappy-java v1.1.10.9
https://github.com/xerial/snappy-java/releases/tag/v1.1.10.9github_commit Patch Available
commit 943c6043a292 (xerial/snappy-java)
Patch available: xerial/snappy-java v1.1.10.9 (contains commit 943c6043a292)
https://github.com/xerial/snappy-java/commit/943c6043a292568575e8347af4507d015e802c75githubMentions a patch (unverified)
Unbounded memory allocation from attacker-declared uncompressed length in snappy-java · Advisory · xerial/snappy-java · GitHub
Affected: 1.1.10.9 (
https://github.com/xerial/snappy-java/security/advisories/GHSA-q233-g92q-qxp6Vendor Advisories for CVE-2026-108106(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-10-09 17:13 UTCGHSA enrichment
- 2026-10-09 15:32 UTCEG score recompute
- 2026-10-09 15:32 UTCGHSA enrichment
- 2026-10-09 14:47 UTCEG score recompute
- 2026-10-09 14:43 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(4)
What is CVE-2026-108106?
CVE-2026-108106 is a high vulnerability published on October 9, 2026. 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…
When was CVE-2026-108106 disclosed?
CVE-2026-108106 was first published on October 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-108106?
CVE-2026-108106 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-108106?
A fix for CVE-2026-108106 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-108106 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108106
Is Your Infrastructure Affected by CVE-2026-108106?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.