WaratekVRT Sign in

CVE-2026-116590

Severity5.9 Medium CVSS 3.1
Fixed in1.1.10.9
WeaknessOut-of-bounds write (CWE-787)
Published26 Oct 2026
Updated30 Oct 2026

Published 19 days ago. NVD often adds the list of affected products days or weeks after a CVE is published, and the other sources we check lag too. The scope and status here may change.

Description

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.

CWE-129

Exploitation status

No public exploit

No exploit has been reported in the sources we check.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment exploitation: none
  • Indexed PoC none indexed
  • EPSS 0.41% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: xerial/snappy-java 2d7ca71.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory
Finding This CVE is MEDIUM severity, is not listed in CISA KEV or VulnCheck KEV, has no public exploit or PoC in any indexed source, carries no CISA Vulnrichment finding of a demonstrated exploit, and is not part of an Oracle Critical Patch Update. None of the signals that would put it in front of an engineer is present, and the volume of CVEs below that bar is too great to take one at a time, so no rule is written for it. This is a decision about what we act on, not a finding that the CVE is harmless — a patch may well be derivable, and a low-severity defect can still be one link in a longer chain.
Candidate fix https://github.com/xerial/snappy-java/commit/2d7ca71c087a98f1219fb2d51909f3891c3ce77b : a commit: the change itself

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.xerial.snappy:snappy-java 0 1.1.10.9 unbounded

Products and versions

1 product, 1 version entry
SourceVendorProductSchemeAffected versions
osv org.xerial.snappy snappy-java generic < 1.1.10.9

References

URLTags
https://github.com/xerial/snappy-java/commit/2d7ca71c087a98f1219fb2d51909f3891c3ce77b commit
https://github.com/xerial/snappy-java/security/advisories/GHSA-xqrx-qh46-34m7 WEB
https://github.com/xerial/snappy-java/pull/741 WEB
https://github.com/xerial/snappy-java PACKAGE
https://github.com/xerial/snappy-java/releases/tag/v1.1.10.9 WEB

Timeline

Published2026-10-26By the CVE Program.
NVD record modified2026-10-30NVD's own last-modified date for this record.