Fix embedded Python StringPrep with one upstream backport - #529
Merged
LouisLotter merged 7 commits intoSep 18, 2026
Merged
LouisLotter merged 7 commits into
LouisLotter merged 7 commits into
Conversation
Copy link
Copy Markdown
Sorry, something went wrong.
Grype 0.112.0 derives a tag-only image's OCI PURL from its source name. On unpublished Docker images the inferred name includes the registry path, so our existing stackstate-k8s-agent VEX subjects do not match. Supplying the product name restores the four existing matches without changing the VEX scope; the same archive still reports the two unassessed Python findings.
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
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.
Fix the reachable StringPrep/IDNA defect (CVE-2026-17084) in embedded Python 3.13.15 with the unchanged upstream 3.13 backport. Retain the packaged-interpreter regression on both architectures and make Omnibus recheck Bazel patch inputs after cache restoration.
Remove five unnecessary backports: four findings already have reviewed VEX; the tar-link path is absent from the supported runtime and has a companion VEX assessment. Also set Grype’s product name so existing image-scoped VEX matches unpublished CI images. This was the reason four resolved findings reappeared in package CI. No scan gate or exception is weakened.
Validation: the published interpreter fails all four IDNA cases and passes with patched StringPrep; patch applies with zero fuzz; Ruff/Ruby checks and offline Zizmor pass. Identical-image Grype controls prove existing VEX matches with the name fix and does not match an unrelated product. Full candidate CI is running. Image-specific fixed VEX awaits verified post-merge digests; Python still reports 3.13.15.
Companion VEX: StackVista/vexhub#43. Detailed audit.
Tracking: https://github.com/StackVista/cve-reporter/issues/29