Skip to content
Fencer Intel
high 7.5

CVE-2026-108106 json

Xerial snappy-java before 1.1.10.9 Unbounded Memory Allocation Denial of Service

published last mo. modified 13d ago also EUVD-2026-95807 , GHSA-q233-g92q-qxp6

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

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.

Patch / fix

  • maven org.xerial.snappy:snappy-java 1.1.10.9
  • xerial snappy-java 1.1.10.9

Is CVE-2026-108106 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-108106 updated cvss 7.5

org.xerial.snappy/snappy-java: snappy-java: Denial of Service via unbounded memory allocation during decompression

  • Red Hat build of Apache Camel 4 for Quarkus 3 snappy-java 1.1.10.8-redhat-00001 Red Hat build of Apache Camel for Spring Boot 4 snappy-java 1.1.10.8-redhat-00001 Red Hat build of Apicurio Registry 3 snappy-java 1.1.10.8-redhat-00001 Red Hat build of Debezium 3 snappy-java 1.1.10.8-redhat-00001 Red Hat build of Quarkus snappy-java 1.1.10.8-redhat-00001
    affected: workaround, no fix available
  • Red Hat Ceph Storage 7 liborc1 Red Hat Ceph Storage 8 liborc1 Red Hat Ceph Storage 9 liborc, liborc2
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Fuse 7 snappy-java 1.1.10.8-redhat-00001
    affected: workaround, no fix planned “Out of support scope”
  • Red Hat JBoss Enterprise Application Platform Expansion Pack snappy-java 1.1.10.8-redhat-00001 Red Hat OpenShift AI (RHOAI) rhoai/odh-spark-operator-rhel9
    affected: workaround, no fix available
  • Red Hat Build of Apache Camel 3.33.4.SP3 snappy-java 1.1.10.11-rhel8-redhat-00001
    fixed: vendor fix RHSA-2026:95622
  • Red Hat Build of Apache Camel 3.33.4.SP3 jimfs 1.1, jna 5.8.0, bcel 6.7.0, gax 2.74.1, icu4j 78.2, joni 2.2.6, +1616 more
    not affected: vulnerable code not present
  • Red Hat JBoss Enterprise Application Platform 8 snappy-java 1.1.10.8-redhat-00001
    not affected: component not present
  • Red Hat Offline Knowledge Portal offline-knowledge-portal/rhokp-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-th-torch-cpu-py312-rhel9, rhoai/odh-th-torch-cuda-py312-rhel9, rhoai/odh-th06-cpu-torch210-py312-rhel9, rhoai/odh-th06-cpu-torch291-py312-rhel9, rhoai/odh-th06-rocm64-torch291-py312-rhel9, rhoai/odh-th06-cuda130-torch210-py312-rhel9, +1 more
    not affected: vulnerable code not in execute path

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
27d ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 4.0 8.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 4.0 8.7 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Affected packages

ecosystem package affected fixed in
maven org.xerial.snappy:snappy-java
<1.1.10.9
1.1.10.9

Affected products

  • xerial snappy-java

Classification

Weakness
  • CWE-789 Memory Allocation with Excessive Size Value
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.