A high-severity vulnerability, tracked as CVE-2025-66566, was discovered in the lz4-java library, which provides LZ4 compression for Java applications. The flaw exists in the Java-based decompressor implementations up to version 1.10.0, where insufficient clearing of the output buffer allows remote attackers to read uninitialized memory by submitting specially crafted compressed input. This could potentially expose sensitive data if the output buffer is reused without being cleared. The vulnerability does not affect JNI-based implementations and has been addressed in version 1.10.1 of the library.
Security advisories highlight that the vulnerability is remotely exploitable and could impact any application using the affected versions of lz4-java for decompression tasks. No specific affected products have been listed yet, but the risk is significant for environments where buffer reuse is common. Users are advised to update to the fixed version to mitigate the risk of information leakage through this flaw.

See affected versions and whether adversaries are exploiting it.
2 events from the most recent confirmed update back to the earliest known activity.
Advisory information recommended upgrading to lz4-java 1.10.1 or later and ensuring output buffers are properly cleared. The disclosure also noted that JNI-based decompressor implementations are not affected.
A high-severity information disclosure flaw affecting yawkat lz4-java up to version 1.10.0 was disclosed. The bug stems from insufficient clearing of the output buffer in the Java safe decompressor, allowing crafted compressed input to expose prior buffer contents when buffers are reused.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
securityonline.info
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.