Bind StringPrep fixed assertion to verified Quay agent digests - #44
Merged
Merged
Conversation
LouisLotter
approved these changes
Sep 19, 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
2 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.
Bind VEX43's existing CVE-2026-17084 fixed assertion to the verified Quay agent index and AMD64/ARM64 manifests from agent529. Six scanner-compatible OCI identifiers cover those three immutable images; all 32 other statements remain unchanged. Tracking #34 and https://github.com/StackVista/cve-reporter/issues/29.
Independent review accepted signed head
ff6655e2ffc952080aef270fa0de23749f8d461b; final CI passed. Evidence and consumer controls distinguish the packaged backport from unpatched images with the same Python version. The final delta corrects the remaining Python CVE in the README.Ready for explicit human VEX binding approval and merge review. That decision is still pending. Published-hub consumption verification and Rancher parity follow an approved merge. Agent511 and GO holds remain; producer-release approval does not approve VEX changes.