[security] Replace net.jpountz.lz4:lz4 with at.yawk.lz4:lz4-java #4696
+23
−23
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
OWASP Dependency Check is failing with the following error, which I believe is unrelated to this change and should be fixed in another PR:
|
zymap
approved these changes
Jan 12, 2026
zymap
pushed a commit
that referenced
this pull request
Jan 12, 2026
(cherry picked from commit b88fb5f)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
net.jpountz.lz4:lz4has been reported to contain multiple vulnerabilities, but it is no longer maintained and users are advised to migrate to the community version,at.yawk.lz4:lz4-java.https://www.sonatype.com/security-advisories/cve-2025-12183
Changes
Pulsar has already done this replacement, so I made a similar change.
apache/pulsar#25032
Migrating to
at.yawk.lz4:lz4-javawill fix the vulnerabilities, but the security advisory also recommends replacing.fastDecompressor()with.safeDecompressor()for better performance.