OESA-2026-4888: snappy-java security update

Published Nov 19, 2026
·
Updated

A Java port of the snappy, a fast compresser/decompresser written in C++. Security Fix(es):

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.(CVE-2026-116590)

Affected Software

1 affected componentFixes available
openeuler/snappy-java<1.1.2.4-6.oe2403sp3
1.1.2.4-6.oe2403sp3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade openeuler/snappy-java to a version that resolves this vulnerability.

    Fixed in 1.1.2.4-6.oe2403sp3
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.1.10.9

Event History

Nov 19, 2026
Advisory Published
via OSV·01:42 AM
Data Sourced
via OSV·01:42 AM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Who is exposed to this issue?

Applications using snappy-java before 1.1.10.9 are exposed if untrusted or otherwise caller-controlled range values can reach Snappy.arrayCopy, SnappyOutputStream.rawWrite, SnappyInputStream.rawRead, or their typed-array read and write methods.

2

What does an attacker need to trigger the vulnerability?

An attacker must be able to supply or influence offsets or byte lengths passed to the affected APIs. Exploitation relies on negative or oversized range values, and typed-array operations may also be affected by integer overflow in byte-size calculations.

3

What is the impact of successful exploitation?

The affected native memcpy call can read or write outside Java array bounds. The described impact is a JVM crash, resulting in denial of service.

4

What version fixes the issue?

Upgrade snappy-java to version 1.1.10.9 or later. Versions prior to 1.1.10.9 are described as affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203