{"id":"CVE-2026-90559","title":"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","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 compress…","severity":"high","cvss":7.5,"cvssVector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","cwe":["CWE-787"],"vendor":"xerial","product":"snappy-java","affected":["snappy-java <= 1.1.10.8"],"published":"2026-09-12","updated":"2026-10-08","sourceUpdated":"2026-10-08T16:17:59.490","source":"NVD","sourceUrl":"https://nvd.nist.gov/vuln/detail/CVE-2026-90559","references":[{"url":"https://github.com/xerial/snappy-java","label":"disclosure@vulncheck.com"},{"url":"https://github.com/xerial/snappy-java/blob/v1.1.10.8/src/main/java/org/xerial/snappy/Snappy.java#L561","label":"disclosure@vulncheck.com"},{"url":"https://github.com/xerial/snappy-java/issues/728","label":"disclosure@vulncheck.com"},{"url":"https://www.vulncheck.com/advisories/snappy-java-through-1.1.10.8-out-of-bounds-write-via-uncompress","label":"disclosure@vulncheck.com"},{"url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-90559.json"},{"url":"https://access.redhat.com/security/cve/CVE-2026-90559"},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=2532603"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-90559"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-90559"}],"tags":["nvd","cve.org","csaf","vex","red-hat"],"ssvc":{"exploitation":"none","automatable":"yes","technicalImpact":"partial","timestamp":"2026-09-14T17:06:13.362626Z"},"epss":0.0063,"epssPercentile":0.49977,"ingestedAt":"2026-09-14T15:23:07.478Z","slug":"CVE-2026-90559","body":"## Overview\n\nsnappy-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.\n\n## Remediation\n\nRefer to the linked advisories for vendor-supplied fixes and affected version ranges.\n\n## Vendor advisories\n\n- **Red Hat VEX** · Important · affected: Red Hat build of Apache Camel 4 for Quarkus 3, Red Hat build of Apache Camel for Spring Boot 4, Red Hat build of Apicurio Registry 3, Red Hat build of Debezium 3, Red Hat build of Quarkus, Red Hat Ceph Storage 7, … · no fix planned: Red Hat Ceph Storage 7, Red Hat Ceph Storage 8, Red Hat Ceph Storage 9, Red Hat build of Apache Camel 4 for Quarkus 3, … · updated 2026-10-09 · [vex](https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-90559.json)","depth":"twilight","depthScore":41,"depthScoreParts":{"impact":41.3,"likelihood":0.1,"exploitation":0,"ransomware":0},"changes":[]}