CVE-2026-90559 json
snappy-java through 1.1.10.8 Out-of-Bounds Write via uncompress
published 2026-09-12 57 d ago modified 2026-10-08 31 d ago also EUVD-2026-76904
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
snappy-java through 1.1.10.8 contains an out-of-bounds write vulnerability in Snappy.uncompress(ByteBuffer, ByteBuffer) because destination buffer capacity is never validated against decompressed size. Attackers can supply valid compressed data that decompresses larger than the destination buffer, causing writes past buffer boundaries and JVM termination.
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-90559 updated cvss 7.5
org.xerial.snappy/snappy-java: snappy-java: Denial of Service via out-of-bounds write
-
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-java Red Hat build of Quarkus snappy-java Red Hat Ceph Storage 7 liborc1affected: workaround, no fix available “Reject untrusted compressed input or enforce a verified maximum decompressed size before invoking the ByteBuffer decompression API.”
+4 more productsfewer
Red Hat Ceph Storage 8 liborc1 Red Hat Ceph Storage 9 liborc, liborc2 Red Hat JBoss Enterprise Application Platform Expansion Pack snappy-java Red Hat OpenShift AI (RHOAI) rhoai/odh-spark-operator-rhel9 -
Red Hat Build of Apache Camel 3.33.4.SP3 snappy-java 1.1.10.11-rhel8-redhat-00001fixed: vendor fix “Reject untrusted compressed input or enforce a verified maximum decompressed size before invoking the ByteBuffer decompression API.” 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 morenot affected: vulnerable code not present
-
Red Hat Fuse 7 snappy-javanot affected: vulnerable code not in execute path
-
Red Hat JBoss Enterprise Application Platform 8 snappy-javanot 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 morenot 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
- 55 d ago
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
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 |
| 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 products
- xerial snappy-java
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
github.com
/xerial/snappy-java/issues/728
issue-tracking
-
github.com
/xerial/snappy-java
product
-
github.com
/xerial/snappy-java/blob/v1.1.10.8/src/main/java/org/xerial/snappy/Snappy.java#L561
technical-description
-
vulncheck.com
/advisories/snappy-java-through-1.1.10.8-out-of-bounds-write-via-uncompress
third-party-advisory
Sources
- CVE List CVE-2026-90559
- NVD CVE-2026-90559
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.