CVE-2025-12183 is a high-severity memory-safety vulnerability in LZ4 Java implementations affecting org.lz4:lz4-java, org.lz4:lz4-pure-java, and net.jpountz.lz4:lz4 through version 1.8.0. The flaw arises from out-of-bounds memory operations during compression or decompression of untrusted LZ4 input. Reported vulnerable components include the deprecated JNI-based fast decompressor and Java-based implementations that rely on sun.misc.Unsafe. When crafted compressed data is processed, the library can access memory outside intended bounds, which may crash the application or expose adjacent memory contents. Implementations that do not use sun.misc.Unsafe reportedly fail with bounds exceptions rather than exhibiting the vulnerable memory access behavior.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Unknown
An out-of-bounds read/memory corruption issue in the lz4-java compression library that can be triggered remotely via untrusted compressed input, leading to denial of service and potential adjacent memory disclosure.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.