CVE-2026-59949
Received Received - Intake

XXHash Buffer Overflow in yawkat LZ4 Java

Publication date: 2026-08-18

Last updated on: 2026-08-18

Assigner: GitHub, Inc.

Description
yawkat LZ4 Java provides LZ4 compression for Java. Prior to 1.11.1, JNI-backed XXHash implementations fail to validate the byte array object and the off and len arguments in XXHashFactory.nativeInstance().hash32().hash(), XXHashFactory.nativeInstance().hash64().hash(), XXHashFactory.nativeInstance().newStreamingHash32().update(), and XXHashFactory.nativeInstance().newStreamingHash64().update(), allowing null arrays or oversized ranges to reach native code, read outside the Java array, and fatally terminate the JVM. This issue is fixed in version 1.11.1.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-18
Last Modified
2026-08-18
Generated
2026-08-18
AI Q&A
2026-08-18
EPSS Evaluated
N/A
NVD
CVE-2026-59949
EUVD
EUVD-2026-60947

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
yawkat lz4-java 1.11.1
yawkat lz4_java 1.11.1

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-476 The product dereferences a pointer that it expects to be valid but is NULL.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the yawkat LZ4 Java library versions prior to 1.11.1. It involves JNI-backed XXHash implementations failing to validate byte array objects and arguments in hash functions. This allows null arrays or oversized ranges to reach native code, causing out-of-bounds reads and JVM crashes.

Detection Guidance

To detect this vulnerability, check the version of lz4-java in use. If it is below 1.11.1, the system is vulnerable. Use commands like 'mvn dependency:tree' in Maven projects or inspect dependency files to verify the version.

Impact Analysis

An attacker could exploit this to crash the JVM by passing invalid inputs to XXHash functions, leading to denial of service. In some cases, it may expose in-process memory, posing a low risk to confidentiality.

Mitigation Strategies

Upgrade to lz4-java version 1.11.1 or later. If upgrading is not possible, validate byte array inputs before calling XXHash APIs or use the safeInstance() alternative which avoids JNI entirely.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-59949. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart