Bug 2510733 (CVE-2026-59949) - CVE-2026-59949 lz4-java: lz4-java: Denial of Service via insufficient validation in XXHash JNI implementations
Summary: CVE-2026-59949 lz4-java: lz4-java: Denial of Service via insufficient validat...
Keywords:
Status: NEW
Alias: CVE-2026-59949
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-08-03 18:41 UTC by OSIDB Bzimport
Modified: 2026-09-01 20:49 UTC (History)
64 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

Description OSIDB Bzimport 2026-08-03 18:41:29 UTC 
Insufficient validation of byte array arguments in JNI-based XXHash implementations in lz4-java 1.11.0 and earlier allows callers to crash the JVM by passing an invalid array reference or invalid range to native XXHash methods. This affects applications where an attacker can influence the byte array object or the off/len arguments passed to affected XXHash APIs.

The primary risk is denial of service through JVM termination. For oversized-length cases, native code may also read memory outside the Java array before crashing, potentially exposing in-process data.

Affected packages:
- at.yawk.lz4:lz4-java <= 1.11.0
- org.lz4:lz4-java <= 1.8.1

Fixed in at.yawk.lz4:lz4-java 1.11.1.

Workaround: Use XXHashFactory.safeInstance() instead of nativeInstance(), as Java-based XXHash implementations are unaffected. Additionally, validate that arrays are non-null and that offset/length parameters fall within array bounds before calling native XXHash methods.
Note You need to log in before you can comment on or make changes to this bug.