Repository navigation
sec: re-add CVE-2025-47273 to trivyignore; python:3.13-slim still ships setuptools 70.3.0 - #287
Merged
Merged
Conversation
…ps setuptools 70.3.0
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
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
Removed in PR #285 expecting
python:3.13-slimto ship fixed setuptools. The production stage already runspip install --upgrade "setuptools>=78.1.1", but Trivy detects the version registered in the base image pip metadata layer (not the upgraded one).release.ymlTrivy gate blocks the Docker release.Evidence
release.ymlrun 41644732836 failed —setuptools 70.3.0 / CVE-2025-47273 / HIGH / fixed: 78.1.1.trivyignorewith rationale; release unblockedMerge Danger
Door: two-way
Blast Radius: config —
.trivyignoreonly. No code changes. Re-tagv0.1.10after merge to re-triggerrelease.yml.