CVE-2025-66566

What it is

yawkat LZ4 Java provides LZ4 compression for Java. Insufficient clearing of the output buffer in Java-based decompressor implementations in lz4-java 1.10.0 and earlier allows remote attackers to read previous buffer contents via crafted compressed input. In applications where the output buffer is reused without being cleared, this may lead to disclosure of sensitive data. JNI-based implementations are not affected. This vulnerability is fixed in 1.10.1.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure.

Exploit odds

0.6% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2025-12-05 18:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-09-25 23:10 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.6% in the next 30 days (EPSS).
• Severity: 8.2 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2025-12-05 18:15 UTC

Last modified

2026-09-25 23:10 UTC

Exploit probability

0.6% · EPSS, next 30 days

Weakness

CWE-201

Record status

Deferred

Attack profile CVSS 4.0 · 8.2

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

None

User interaction

None

Confidentiality

High

Integrity

None

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2025-66566.md and follow it. Check whether this project is affected by CVE-2025-66566. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge