Quick answers
- Is CVE-2026-116590 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116590 being exploited in the wild.
- How severe is CVE-2026-116590?
- Medium severity, with a CVSS score of 5.9, published 26 October 2026.
- Which products and versions are affected?
- org.xerial.snappy:snappy-java (Maven) <= 1.1.10.8, ECOSYSTEM:introduced=0,fixed=1.1.10.9; Xerial Snappy-Java before 1.1.10.9.
- Is there a fix for CVE-2026-116590?
- Yes. org.xerial.snappy:snappy-java (Maven): upgrade to 1.1.10.9 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116590 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-116590?
- Check whether you run org.xerial.snappy:snappy-java (Maven) or Xerial Snappy-Java at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.xerial.snappy:snappy-java (Maven): upgrade to 1.1.10.9 or later
# set org.xerial.snappy:snappy-java to 1.1.10.9 in your pom.xml or build.gradle
Technical details
The Snappy.arrayCopy() method passes caller-supplied offset and length parameters to native memcpy without validating array bounds, allowing negative or oversized values to access memory outside the intended arrays. SnappyOutputStream.rawWrite() and SnappyInputStream.rawRead() rely on this primitive, and integer overflow in typed-array byte-size calculations compounds the issue. The vulnerability is fixed by adding bounds validation before the native call.
Affected products
- Xerial snappy-java before 1.1.10.9
Identifiers
- CVE-2026-116590
- GHSA-xqrx-qh46-34m7
Timeline
- 2026-10-03: patched
- 2026-10-26: advisory