Summary
LZ4 Java Compression has Out-of-bounds memory operations which can cause DoS
Out-of-bounds memory operations in org.lz4:lz4-java 1.8.0 and earlier allow remote attackers to cause denial of service and read adjacent memory via untrusted compressed input.
This is fixed in a forked release: at.yawk.lz4:lz4-java version 1.8.1. The original project has been archived: https://github.com/lz4/lz4-java, and Sonatype has added a redirect from org.lz4:lz4-java:1.8.1 to the new group ID.
Impact
A read operation accesses a memory location beyond the intended buffer boundary. Typical impact: sensitive data disclosure or crash.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
at.yawk.lz4:lz4-java to 1.8.1 or later; org.lz4:lz4-java to 1.8.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-12183? CVE-2025-12183 is a high-severity out-of-bounds read vulnerability in at.yawk.lz4:lz4-java (maven), affecting versions < 1.8.1. It is fixed in 1.8.1. A read operation accesses a memory location beyond the intended buffer boundary.
- Which packages are affected by CVE-2025-12183?
at.yawk.lz4:lz4-java(maven) (versions < 1.8.1)org.lz4:lz4-java(maven) (versions < 1.8.1)org.lz4:lz4-pure-java(maven) (versions <= 1.8.0)net.jpountz.lz4:lz4(maven) (versions <= 1.3.0)
- Is there a fix for CVE-2025-12183? Yes. CVE-2025-12183 is fixed in 1.8.1. Upgrade to this version or later.
- Is CVE-2025-12183 exploitable, and should I be worried? Whether CVE-2025-12183 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-12183 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-12183?
- Upgrade
at.yawk.lz4:lz4-javato 1.8.1 or later - Upgrade
org.lz4:lz4-javato 1.8.1 or later
- Upgrade