CVE-2025-12183
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOut-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOut-of-bounds memory operations in lz4-java versions 1.8.0 and earlier allow remote attackers to cause denial of service and read adjacent memory via untrusted compressed input. This is a memory safety vulnerability in the compression library where malformed compressed data can trigger reads beyond buffer boundaries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Find lz4-java library in your projectSearch your project dependencies for lz4-java (also known as net.jpountz.lz4:lz4-java) by checking your Maven pom.xml, Gradle build.gradle, or inspecting the JAR files in your classpathAffected if lz4-java is present in your dependencies or classpath
-
Determine the exact version installedLocate the lz4-java JAR file or dependency declaration and note the version number (for example, look for lz4-java-1.8.0.jar or in your dependency management)Affected if The version is 1.8.0 or any version earlier than 1.8.0
-
Check if your application processes compressed inputReview your code to determine whether lz4-java is used to decompress data that comes from untrusted or external sources, such as user uploads, network streams, or files handled by your applicationAffected if Your application decompresses data using lz4-java from untrusted or external sources (this is the attack vector for the vulnerability)
You are affected if lz4-java version 1.8.0 or earlier is present in your environment AND your application uses it to decompress untrusted compressed input, because the out-of-bounds memory read requires the vulnerable code path to be invoked with malformed data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade lz4-java to the latest patched version (1.8.1 or later) and validate that all compression/decompression functionality continues to work correctly after the upgrade.
org.lz4:lz4-java version 1.8.1 or later
- 1. Identify all Maven/Gradle dependencies that reference org.lz4:lz4-java in your project
- 2. Run a dependency tree command (e.g., mvn dependency:tree or gradle dependencies) to confirm the current version in use
- 3. Update the dependency version to 1.8.1 or later in your build configuration (pom.xml or build.gradle)
- 4. Rebuild and test your application to verify the library upgrade does not cause regressions
- 5. Verify the fix is applied by checking that the lz4-java version resolves to 1.8.1 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12183 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12183 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data