CVE-2026-93451 json
snappy-java through 1.1.10.8 Buffer Overflow via typed uncompress methods
published 2026-09-17 52 d ago modified 2026-10-27 12 d ago also GHSA-gwq9-9ffj-mvrv , EUVD-2026-82603
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
snappy-java through 1.1.10.8 contains a buffer overflow vulnerability in typed Snappy.uncompress*Array methods that allocate output arrays by dividing uncompressed length by element size but pass the undivided length to native code. Attackers controlling compressed input can cause misaligned length values to write past array bounds with attacker-controlled bytes, corrupting heap memory.
Patch / fix
- maven org.xerial.snappy:snappy-java 1.1.10.9
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-93451 updated cvss 6.5
org.xerial/snappy-java: snappy-java: Buffer overflow via malformed compressed input
-
Red Hat build of Apache Camel 4 for Quarkus 3 snappy-java Red Hat build of Apache Camel for Spring Boot 4 snappy-java Red Hat build of Apicurio Registry 3 snappy-java Red Hat build of Debezium 3 snappy-javaaffected: workaround, no fix available “Fix deferred”
-
Red Hat build of Quarkus snappy-javaaffected: workaround, no fix available
-
Red Hat Ceph Storage 8 liborc1 Red Hat Ceph Storage 9 liborc, liborc2 Red Hat Fuse 7 snappy-java Red Hat JBoss Enterprise Application Platform 8 snappy-java Red Hat JBoss Enterprise Application Platform Expansion Pack snappy-java Red Hat Offline Knowledge Portal offline-knowledge-portal/rhokp-rhel9affected: workaround, no fix available “Fix deferred”
+1 more productsfewer
Red Hat OpenShift AI (RHOAI) rhoai/odh-spark-operator-rhel9, 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, +2 more
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
- 48 d ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L |
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/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 |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
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
References
-
github.com
/xerial/snappy-java/pull/739
web
-
github.com
/xerial/snappy-java/commit/943c6043a292568575e8347af4507d015e802c75
web
-
github.com
/xerial/snappy-java/issues/729
issue-tracking, web
-
github.com
/xerial/snappy-java/blob/v1.1.10.8/src/main/java/org/xerial/snappy/Snappy.java#L802
technical-description, web
-
github.com
/xerial/snappy-java
product, package
-
vulncheck.com
/advisories/snappy-java-through-1.1.10.8-buffer-overflow-via-typed-uncompress-methods
third-party-advisory, web
-
github.com
/xerial/snappy-java/security/advisories/GHSA-gwq9-9ffj-mvrv
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-93451
advisory
-
github.com
/xerial/snappy-java/releases/tag/v1.1.10.9
web
Sources
- CVE List CVE-2026-93451
- GitHub Advisory GHSA-gwq9-9ffj-mvrv
- NVD CVE-2026-93451
Fencer Vulns 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.