Assess agent tar-link applicability and record the StringPrep fix - #43
Merged
Merged
Conversation
rb3ckers
approved these changes
Sep 18, 2026
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
3 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.
Add an image-scoped
not_affectedassessment for tar-link CVE-2026-87910 and afixedstatement for the exact StringPrep source commit in agent PR529.AMD64/ARM64 inspection of published agent
13451dce(indexsha256:32a25b904072a24df3c6e1d3da22e8fb7fee9e34ad98b4a73756b091acba4060) found identical tar call-site files: runtime readers useextractfile; filtered filesystem extraction belongs to unused build tooling. This assertion covers shipped integrations, not arbitrary customer checks.Grype controls apply the four existing Python statements plus tar-link, leaving StringPrep active; an unrelated image name suppresses none. Index validation passes. The
fixedstatement deliberately identifies source only: add verified published image digests after PR529 merges, then verify both scanner consumers. It does not clear unpatched Python 3.13.15 images.Detailed audit and publication handoff.
Tracking: #34 and https://github.com/StackVista/cve-reporter/issues/29. Rancher migration remains a post-merge follow-up.