CVE-2026-116590 json
snappy-java: JVM crash from unchecked ranges in Snappy.arrayCopy and SnappyOutputStream.rawWrite
published 2026-10-26 13 d ago modified 2026-10-30 9 d ago also GHSA-xqrx-qh46-34m7 , EUVD-2026-110473
- cvss
- 5.9
- 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 35%
- public exploits
- 0
- none known
Summary
snappy-java is a Java port of the snappy, a fast C++ compresser/decompresser developed by Google. Prior to 1.1.10.9, Snappy.arrayCopy(Object src, int offset, int byteLength, Object dest, int destOffset) passes caller-supplied ranges to native memcpy without validating either array, allowing negative or oversized byteLength and offset values to read or write outside array bounds and crash the JVM. SnappyOutputStream.rawWrite and SnappyInputStream.rawRead, including their typed-array write and read methods, pass caller-controlled ranges through this primitive, and typed-array byte-size calculations can overflow int. This issue is fixed in version 1.1.10.9.
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-116590 updated cvss 5.9
org.xerial.snappy/snappy-java: snappy-java: Denial of Service via out-of-bounds memory access
-
Red Hat OpenShift Serverless openshift-serverless-1/kn-ekb-receiver-rhel9, openshift-serverless-1/kn-ekb-dispatcher-rhel9 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-00001affected: workaround, no fix available “Fix deferred”
-
Red Hat build of Quarkus snappy-java 1.1.10.8-redhat-00001affected: workaround, no fix available
-
Red Hat Ceph Storage 7 liborc1 Red Hat Ceph Storage 8 liborc1affected: workaround, no fix available “Fix deferred”
-
Red Hat Ceph Storage 9 liborc, liborc2 Red Hat Fuse 7 snappy-java 1.1.10.8-redhat-00001affected: workaround, no fix planned “Out of support scope”
-
Red Hat Offline Knowledge Portal offline-knowledge-portal/rhokp-rhel9 Red Hat OpenShift AI (RHOAI) rhoai/odh-spark-operator-rhel9, rhoai/odh-trustyai-service-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, +3 more Red Hat streams for Apache Kafka 3 snappy-java 1.1.10.8-redhat-00001affected: workaround, no fix available “Fix deferred”
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
- no
- Technical impact
- partial
- Assessed
- 9 d ago
Exploit prediction
0.41% chance of exploitation in the next 30 days, higher than 35% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/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/741
web
-
github.com
/xerial/snappy-java/commit/2d7ca71c087a98f1219fb2d51909f3891c3ce77b
web
-
github.com
/xerial/snappy-java/security/advisories/GHSA-xqrx-qh46-34m7
web
-
github.com
/xerial/snappy-java/releases/tag/v1.1.10.9
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-116590
advisory
-
github.com
/xerial/snappy-java
package
Sources
- CVE List CVE-2026-116590
- GitHub Advisory GHSA-xqrx-qh46-34m7
- NVD CVE-2026-116590
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.