fix(QTDI-3283): CVE-2026-49844 upgrade Log4j to 2.25.5 - #1263
Open
pyzhou-talend wants to merge 1 commit into
Open
fix(QTDI-3283): CVE-2026-49844 upgrade Log4j to 2.25.5#1263pyzhou-talend wants to merge 1 commit into
pyzhou-talend wants to merge 1 commit into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
pyzhou-talend
changed the title
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Requirements
Why this PR is needed?
Log4j 2.20.0 is affected by CVE-2026-49844. The minimum safe same-major release is 2.25.5.
What does this PR adds (design/code thoughts)?
Upgrades the centralized Log4j version property to 2.25.5. No API or runtime logic is changed. Dependency resolution was checked; the default build is blocked by the repository's missing external Spotless formatter file.
Review
Mandatory scope/design and standards/compliance reviews reran with no actionable findings.
AI generated code
https://internal.qlik.dev/general/ways-of-working/code-reviews/#guidelines-for-ai-generated-code