cve.bz

CVE-2026-59949 yawkat lz4-java: NULL Pointer Dereference

6.5 mediumEPSS 0.5%Fix available

Medium (6.5) in yawkat lz4-java. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in at.yawk.lz4:lz4-java 1.11.1.

On this page
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.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 41st percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-476 NULL Pointer Dereference
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-59949 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-59949?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-59949?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-59949 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
yawkat lz4-java< 1.11.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-xx22-p4ch-683rMavenat.yawk.lz4:lz4-java<1.11.11.11.1
GHSA-xx22-p4ch-683rMavenorg.lz4:lz4-java<=1.8.1no fix published

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13lz4-javano fix listedDEBIAN-CVE-2026-59949
Debian14lz4-java1.11.2+ds1-1DEBIAN-CVE-2026-59949
Ubuntu20.04:LTS, 22.04:LTS, 24.04:LTS and 2 morelz4-javano fix listedUBUNTU-CVE-2026-59949

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

A flaw was found in the lz4-java library's JNI-backed XXHash implementations. The native XXHash methods (hash32, hash64, streamingHash32, streamingHash64) obtained via XXHashFactory.nativeInstance() do not properly validate byte array arguments, offsets, and lengths before passing them to native code. An attacker able to control these parameters can pass null arrays or out-of-bounds ranges, causing a fatal JVM crash (denial of service) and potentially reading process memory beyond array bounds. The Java-based implementations obtained via XXHashFactory.safeInstance() or XXHashFactory.fastestJavaInstance() are not affected.

Red Hat's mitigation

Use XXHashFactory.safeInstance() or XXHashFactory.fastestJavaInstance() instead of XXHashFactory.nativeInstance() to avoid the JNI boundary. Alternatively, validate that arrays are non-null and that offset and length parameters describe a range fully contained in the array before calling native XXHash methods.

ProductPackageStateAdvisory
Red Hat build of Quarkus 3.27.6.redhatat.yawk.lz4/lz4-java:1.11.1.rhel8-redhat-00001Fixed 2026-10-15RHSA-2026:83082
Red Hat build of Quarkus 3.33.4.redhatat.yawk.lz4/lz4-java:1.11.1.rhel8-redhat-00001Fixed 2026-10-15RHSA-2026:83520
OpenShift Developer Tools and Servicesjenkins-2-pluginsFix deferred
OpenShift Developer Tools and Servicesocp-tools-4/jenkins-rhel8Fix deferred
OpenShift Developer Tools and Servicesocp-tools-4/jenkins-rhel9Fix deferred
Red Hat build of Apache Camel 4 for Quarkus 3lz4-javaFix deferred
Red Hat build of Apache Camel for Spring Boot 4liblz4-java.soFix deferred
Red Hat build of Apache Camel for Spring Boot 4lz4-javaFix deferred
Red Hat build of Apicurio Registry 3lz4-javaFix deferred
Red Hat build of Debezium 3lz4-javaFix deferred
Red Hat Enterprise Linux 8jmc:rhel8/lz4-javaFix deferred
Red Hat Enterprise Linux 8lz4-javaFix deferred
Red Hat Enterprise Linux 9jmcFix deferred
Red Hat Fuse 7lz4-javaFix deferred
Red Hat Hardened Imagesmaven3.9Fix deferred
Red Hat JBoss Enterprise Application Platform 8liblz4-java.soFix deferred
Red Hat JBoss Enterprise Application Platform 8lz4-javaFix deferred
Red Hat JBoss Enterprise Application Platform Expansion Packliblz4-java.soFix deferred
Red Hat JBoss Enterprise Application Platform Expansion Packlz4-javaFix deferred
Red Hat OpenShift AI (RHOAI)rhoai/odh-spark-operator-rhel9Fix deferred
7 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-59949.

References

Check your stackJSON