CVE-2026-116590: snappy-java security update
Affects snappy-javaSource GCVE Database
Not known to be exploited · CVSS 5.9 Medium : upgrade to 1.1.2.4-6.oe2403sp1 when convenient.
Data as of 19 Nov 2026, 03:52 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 5.9 |
|---|
- Patch
- Available – fixed in 1.1.2.4-6.oe2403sp1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade snappy-java to 1.1.2.4-6.oe2403sp1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
openEuler 24.03-LTS-SP1snappy-javapkg:rpm/openEuler/snappy-java&distro=openEuler-24.03-LTS-SP1Other threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade snappy-java to version 1.1.10.9 or later, where the issue is fixed. No other mitigation is indicated or required.
Description
A vulnerability in snappy-java prior to version 1.1.10.9 allows passing of unvalidated array ranges to native memcpy, which can cause out-of-bounds reads or writes and crash the JVM. This is due to lack of validation on offset and byteLength parameters in Snappy.arrayCopy and related methods. The issue is fixed in version 1.1.10.9.