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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-12183 can be triaged on real exposure rather than presence alone.

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 51th 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 August 12, 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

Not in CISA KEV

CVE-2025-12183 — lz4-java

CVE-2025-12183 is a Out-of-bounds Read vulnerability in at.yawk.lz4:lz4-java. A fix is available for at.yawk.lz4:lz4-java — see the affected versions and patch details below.

org.lz4:lz4-java - Out-of-Bounds Memory Access

Also known asGHSA-vqf4-7m7x-wgfc

Published

Nov 28, 2025

Updated

Aug 12, 2026

Affected

4 pkgs

Patched

2 / 4

Exploits

None indexed

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-12183.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs51th percentile — riskier than 51% of all scored CVEsHighest risk

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.

Real-World Exposure

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.

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.

Affected Packages

4 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`at.yawk.lz4:lz4-java`	all versions	1.8.1`at.yawk.lz4:lz4-java:1.8.1`
☕Maven	`org.lz4:lz4-java`	all versions	1.8.1`org.lz4:lz4-java: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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2025-12183 can be triaged on real exposure rather than presence alone.

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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This vulnerability affects the "fast" decompressor, this is due to the fact such implementation relies on LZ4_decompress_fast API of the lz4 C library. This function was deprecated in the lz4 library as it misses boundary checks and is considered insecure when processing untrusted inputs. Red Hat has considered this…

Product	Fixed in	Advisory
Red Hat build of Quarkus 3.20.4.SP1	`lz4-java`	RHSA-2026:0131
Red Hat build of Quarkus 3.27.1.SP1	`lz4-java`	RHSA-2026:0134
Red Hat JBoss Enterprise Application Platform 8.1	see advisory	RHSA-2026:1872
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 8	`eap8-wildfly-0:8.1.4-2.GA_redhat_00005.1.el8eap`	RHSA-2026:1870
Red Hat JBoss Enterprise Application Platform 8.1 for RHEL 9	`eap8-wildfly-0:8.1.4-2.GA_redhat_00005.1.el9eap`	RHSA-2026:1871

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. 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.

O3 Security · Impact-Aware SCA

Is CVE-2025-12183 in your dependencies?

O3 Security finds CVE-2025-12183 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works