CVE-2026-108106

waiting for further signalsZero needs more public information before it can validate it.

GHSA-94x4-5g3f-jjxp ↗EUVD-2026-95807 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
xerial snappy-java <= 1.1.10.8
fixed in 1.1.10.9
CWE-789 Memory Allocation with Excessive Size Value
ETK-2026-1079Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:maven/org.xerial.snappy/snappy-java
11d 13h 30msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h47m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Xerial snappy-java versions earlier than 1.1.10.9 can allocate excessive JVM heap memory while handling malformed compressed data. An attacker may cause a denial of service if they can cause application-controlled decompression APIs to process attacker-supplied input.

mitigation

Upgrade snappy-java to version 1.1.10.9 or later. Until upgraded, do not pass untrusted compressed data to the affected decompression paths.

fixed in 1.1.10.9

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.37%29th percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-09 14:33Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-09 14:33Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-108106

{
  "etk_id": "ETK-2026-1079",
  "cve_id": "CVE-2026-108106",
  "display_id": "CVE-2026-108106",
  "ghsa_id": "GHSA-94x4-5g3f-jjxp",
  "euvd_id": "EUVD-2026-95807",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unbounded memory allocation in xerial snappy-java",
  "summary": "Xerial snappy-java versions earlier than 1.1.10.9 can allocate excessive JVM heap memory while handling malformed compressed data. An attacker may cause a denial of service if they can cause application-controlled decompression APIs to process attacker-supplied input.",
  "mitigation": "Upgrade snappy-java to version 1.1.10.9 or later. Until upgraded, do not pass untrusted compressed data to the affected decompression paths.",
  "vendor": "xerial",
  "product": "snappy-java",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 1.1.10.8"
      ],
      "ecosystem": "maven",
      "fixed_versions": [
        "1.1.10.9"
      ],
      "package_name": "org.xerial.snappy:snappy-java",
      "purl": "pkg:maven/org.xerial.snappy/snappy-java"
    }
  ],
  "cwes": [
    789
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "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",
  "epss_score": 0.0037,
  "epss_percentile": 0.2964,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 10.903654833333333,
  "t0_at": "2026-10-09T14:33:29.499000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-09T14:33:29.499000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-09T14:33:29.499000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108106"
    }
  }
}

published 2026-10-09 15:09Z
last change 2026-10-21 04:45Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.