This repository was archived by the owner on Jan 7, 2026. It is now read-only.
logstash-[9.2]: Update advisory for CVE-2025-14762 #28187
Merged
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
auto-merge was automatically disabled
December 29, 2025 19:57
Pull request was converted to draft
ca-scribner
force-pushed
the
logstash/GHSA-2xgq-q749=89fq
branch
2 times, most recently
from
24e935a to
76a6515
Compare
To mitigate CVE-2025-14762, log4j must be bumped from 2.17.2 to 2.25.3. This includes navigating a few small breaking changes in log4j. Upstream is currently working on a patch to complete this migration [here](elastic/logstash#18522), but the patch is incomplete and has failing tests
ca-scribner
force-pushed
the
logstash/GHSA-2xgq-q749=89fq
branch
from
76a6515 to
c23b786
Compare
bentasker
approved these changes
Dec 30, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
To mitigate CVE-2025-14762, log4j must be bumped from 2.17.2 to 2.25.3. This includes navigating a few small breaking changes in log4j. Upstream is currently working on a patch to complete this migration here, but the patch is incomplete and has failing tests