Renew log4j 1.2.17 reference suppression to 2026-06-01#287
Merged
Conversation
Suppression expired 2026-05-01. Renewed; the log4j 1.2.17 jar is a reference-only dependency used by the migration recipe to identify the legacy log4j artifact, not loaded at runtime. Refs moderneinc/dependency-vulnerability-reports#1054
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.
Summary
The suppression for the log4j 1.2.17 reference jar expired on 2026-05-01. The jar is shipped only so the migration recipe can identify the legacy log4j artifact — it isn't loaded at runtime, so the CRITICAL CVEs against it remain non-exploitable in this context. Renewed
until="2026-06-01Z".Test plan