Xerial snappy-java from 1.1.7.4 before 1.1.10.10 contains a double release vulnerability in SnappyFramedInputStream that returns pooled buffers twice when replacement allocation fails. Attackers can supply framed data with a large declared chunk length to trigger OutOfMemoryError, causing shared backing arrays that expose or overwrite other streams' decompressed data.
CVE-2026-108104
MEDIUMPre-NVD 4.84.8—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 4.8 from GitHub Security Advisory published 2026-10-09. A secondary CVSS source baseline 4.8; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
4.8EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 4.8Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 4.8
- EG Score
- 4.8MEDIUMhigh confidence
- EG Risk
- 22EG Risk 22/100
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 computed (value × EchelonGraph’s weight)Severity48% × 45%The EG Score, 4.8 of 10.Exploitation0.2% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.2%
- EPSS %ILE
- 10th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 9, 2026
Last Modified
October 9, 2026
Advisory Details (6)
Auto-updated Oct 9, 2026Patch available. Sources: github, github_commit, github_release.
Web page
Xerial snappy-java 1.1.7.4 before 1.1.10.10 Double Release of Pooled Buffers in SnappyFramedInputStream | Advisories | VulnCheck
https://www.vulncheck.com/advisories/xerial-snappy-java-1.1.7.4-before-1.1.10.10-double-release-of-pooled-buffers-in-snappyframedinputstreamWeb page
GitHub - xerial/snappy-java: Snappy compressor/decompressor for Java · GitHub
https://github.com/xerial/snappy-javaWeb page
snappy-java/src/main/java/org/xerial/snappy/SnappyFramedInputStream.java at v1.1.10.9 · xerial/snappy-java · GitHub
https://github.com/xerial/snappy-java/blob/v1.1.10.9/src/main/java/org/xerial/snappy/SnappyFramedInputStream.java#L243GitHub release Patch Available
v1.1.10.10
Patch available: xerial/snappy-java v1.1.10.10
https://github.com/xerial/snappy-java/releases/tag/v1.1.10.10GitHub commit Patch Available
commit 139a53090a66 (xerial/snappy-java)
Patch available: xerial/snappy-java v1.1.10.10 (contains commit 139a53090a66)
https://github.com/xerial/snappy-java/commit/139a53090a6662298924fd75d21f4769b4a219eaGitHub advisoryMentions a patch (unverified)
Double release of pooled buffers in SnappyFramedInputStream can share a buffer across streams · Advisory · xerial/snappy-java · GitHub
Affected: 1.1.10.10 (
https://github.com/xerial/snappy-java/security/advisories/GHSA-c73m-r934-8qvgVendor Advisories for CVE-2026-108104(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(3 across 3 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| snappy-java | 1.1.10.5-1, 1.1.10.5-2, 1.1.10.7-1, 1.1.10.8-1, 1.1.8.3-1 |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| snappy-java | 1.1.10.7-1, 1.1.10.8-1 |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| snappy-java | 1.1.10.7-1, 1.1.10.8-1 |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-11 20:32 UTCGHSA enrichmentGHSA-2xrm-qggp-hr4m · GitHub CVSS 4.8
- 2026-10-11 20:14 UTCEG score recompute
- 2026-10-11 18:26 UTCEG score recompute
- 2026-10-11 15:00 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 10th percentile
- 2026-10-10 18:50 UTCGHSA enrichmentGHSA-2xrm-qggp-hr4m · GitHub CVSS 4.8
- 2026-10-09 17:13 UTCGHSA enrichmentGHSA-2xrm-qggp-hr4m · GitHub CVSS 4.8
- 2026-10-09 15:32 UTCEG score recompute
- 2026-10-09 15:32 UTCGHSA enrichmentGHSA-2xrm-qggp-hr4m · GitHub CVSS 4.8
- 2026-10-09 14:47 UTCEG score recomputeFirst assessed: 4.8 MEDIUM
- 2026-10-09 14:43 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-108104?
CVE-2026-108104 is a medium-severity vulnerability; its CVE record was published on October 9, 2026. Xerial snappy-java from 1.1.7.4 before 1.1.10.10 contains a double release vulnerability in SnappyFramedInputStream that returns pooled buffers twice when replacement allocation fails. Attackers can supply framed data with a large declared chunk length to trigger OutOfMemoryError, causing shared…
When was CVE-2026-108104 made public?
CVE-2026-108104 was made public on October 3, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on October 9, 2026. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-108104 actively exploited?
CVE-2026-108104 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-108104?
CVE-2026-108104 has a CVSS base score of 4.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-108104?
A fix for CVE-2026-108104 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-108104 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-108104
Is Your Infrastructure Affected by CVE-2026-108104?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.