How severe is CVE-2025-12183?

No CVSS score has been assigned to CVE-2025-12183 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-12183?

CVE-2025-12183 affects the following packages: at.yawk.lz4:lz4-java (Maven), org.lz4:lz4-java (Maven), org.lz4:lz4-pure-java (Maven), net.jpountz.lz4:lz4 (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-12183?

Update at.yawk.lz4:lz4-java to 1.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-12183 is resolved across your whole dependency graph.

How do I detect CVE-2025-12183 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for at.yawk.lz4:lz4-java. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2025-12183 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2025-12183?

O3 pinpoints whether CVE-2025-12183 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2025-12183 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-12183 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-12183?

CVE-2025-12183 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-12183?

CVE-2025-12183 is classified as Out-of-bounds Read (CWE-125). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-12183 published, and has it been updated?

CVE-2025-12183 was published on November 28, 2025 and was last updated on March 23, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

CVE-2025-12183

LZ4 Java Compression has Out-of-bounds memory operations which can cause DoS

Also known asGHSA-vqf4-7m7x-wgfc

Published

Nov 28, 2025

Updated

Mar 23, 2026

Affected

4 pkgs

Patched

2 / 4

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk48th percentile+0.58%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

☕at.yawk.lz4:lz4-java☕org.lz4:lz4-java☕org.lz4:lz4-pure-java☕net.jpountz.lz4:lz4

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

4 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`at.yawk.lz4:lz4-java`	all versions	1.8.1
☕Maven	`org.lz4:lz4-java`	all versions	1.8.1
☕Maven	`org.lz4:lz4-pure-java`	all versions	No fix
☕Maven	`net.jpountz.lz4:lz4`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for at.yawk.lz4:lz4-java. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update at.yawk.lz4:lz4-java to 1.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-12183 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-12183 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-12183. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2025-12183 in your dependencies?

O3 detects CVE-2025-12183 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works