fix(deps): update dependency at.yawk.lz4:lz4-java to v1.10.1 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
at.yawk.lz4:lz4-java	1.8.1 -> 1.10.1

GitHub Vulnerability Alerts

CVE-2025-66566

Summary

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.

Details

During the decompression process, the lz4 algorithm may have to repeat data that was previously decompressed in the same input frame. In the Java implementation, this is implemented by copy operations within the output buffer.

With a crafted input, an attacker may induce the Java implementation to copy from a region in the output buffer that does not contain decompressed data yet. If that region contains sensitive information because the output buffer was not cleared prior to decompression, that data will then be copied to the decompressed output.

• LZ4Factory.nativeInstance().safeDecompressor() is not affected.
• LZ4Factory.nativeInstance().fastDecompressor() is affected because it actually uses safeInstance() since 1.8.1. In 1.8.0 and earlier versions, this implementation is instead vulnerable to the more severe CVE‐2025‐12183, so downgrading is not a solution.
• Both decompressors of LZ4Factory.safeInstance(), LZ4Factory.unsafeInstance() and LZ4Factory.fastestJavaInstance() are affected.
• LZ4Factory.fastestInstance() uses the nativeInstance or fastestJavaInstance depending on platform. LZ4Factory.fastestInstance().fastDecompressor() is always affected, while LZ4Factory.fastestInstance().safeDecompressor() is affected only when JNI cannot be used (e.g. on unsupported platforms).

Independent of this vulnerability, it is recommended that users migrate from fastDecompressor to safeDecompressor, as the latter is more performant (despite the name).

The impact of this vulnerability depends on how user code interacts with the decompression API. Users that allocate a new destination buffer each time, or use only zeroed buffers, are not impacted. When the buffer is reused, however, the confidentiality impact can be severe. This vulnerability is marked as VC:H out of caution.

Mitigation

lz4-java 1.10.1 fixes this issue without requiring changes in user code.

If you cannot upgrade to 1.10.1, you can mitigate this vulnerability by zeroing the output buffer before passing it to the decompression function.

Relation to CVE‐2025‐12183

This CVE is a different attack than CVE‐2025‐12183, affecting different implementations with different impact. This new vulnerability was discovered by CodeIntelligence during research that followed up on CVE‐2025‐12183. Users are recommended to upgrade to 1.10.1 to fix both vulnerabilities.

---

Release Notes

yawkat/lz4-java (at.yawk.lz4:lz4-java)

v1.10.1: lz4-java v1.10.1

Compare Source

Contains fix for CVE-2025-66566!

What's Changed

• Add test for corrupted LZ4 block input stream by @​Marcono1234 in #​7
• Update documentation for checksum registration by @​yawkat in #​8
• Migrate to maven-git-versioning-extension by @​yawkat in #​10
• Add workflow_dispatch trigger to multi-platform build to allow testing without release by @​yawkat in #​13
• Copy native libraries to target/classes instead of src/resources by @​yawkat in #​14

Full Changelog: yawkat/lz4-java@v1.10.0...v1.10.1

v1.10.0: lz4-java v1.10.0

Compare Source

This release does not contain security-relevant changes. It was made for #​3, so that users of LZ4BlockInputStream can migrate to safeDecompressor() to mitigate the performance impact of the CVE‐2025‐12183 patch. Note that this still requires a change in user code.

What's Changed

• Replace old repository links & improve README by @​Marcono1234 in #​2
• Remove unused POM template files by @​Marcono1234 in #​1
• Hide util package from Javadoc by @​Marcono1234 in #​4
• Allow to create LZ4BlockInputStream with LZ4SafeDecompressor by @​meshcow in #​3
• Fix remaining ArrayIndexOutOfBoundsExceptions in LZ4DecompressorTest by @​Marcono1234 and @​yawkat in #​6

New Contributors

• @​Marcono1234 made their first contribution in #​2
• @​meshcow made their first contribution in #​3
• @​yawkat made their first contribution in #​6

Full Changelog: yawkat/lz4-java@v1.9.0...v1.10.0

v1.9.0: lz4-java v1.9.0

Compare Source

• Replace ant-based build with maven (@​yawkat)
• Use multi-platform GitHub actions for native library build (@​yawkat)
• Update lz4 to v1.10.0 (@​yawkat)
• Improve Java implementation bounds checking and tests (@​yawkat and @​Marcono1234)

Unsafe implementations should be secure now, but are not yet enabled by default.

Full Changelog: yawkat/lz4-java@v1.8.1...v1.9.0

---

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.