Renew the GO-2026-5932 scan exception - #264
Open
ai-collaboration-app[bot] wants to merge 2 commits into
Open
Conversation
The vexhub statement now suppresses this advisory for both scanners, so the local exception is redundant as well as expired (2026-08-26). Verified against a representative amd64 image built from this commit with the scanner versions CI pins (Trivy 0.70.0, Grype 0.112.0). Without the VEX repo both scanners report GO-2026-5932 against golang.org/x/crypto v0.53.0, and Grype additionally reports three containerd v1.7.33 advisories; with the repo configured the way the scan-image action configures it, all four are suppressed and the evaluator reports this exception as unused. The openpgp packages remain absent from the binary: `go list -deps ./cmd/...` resolves 1335 packages with no openpgp package, and the only linked x/crypto packages are pbkdf2, scrypt and ocsp. exceptions/.gitkeep keeps the directory present because ci.yml passes exceptions-path: exceptions, and the scan-image action fails when that path does not exist. Co-authored-by: Cve Ticket Reconciler <cve-ticket-reconciler@stackstate.invalid>
CI disproved the premise of the previous commit. Run 33075037844 reported the advisory as unmanaged on both architectures once the exception was gone, while the containerd statements in the same vexhub document kept matching — so the vexhub statement does not cover the pre-publication commit image after all. A local rebuild using the same vexhub repository and the same pinned scanner versions did suppress it, so the divergence is environmental. The most likely cause is image identity rather than the statement: a locally loaded image carries a RepoDigest and Trivy derives its OCI product purl from that digest, while the CI image is built with load: true and never pushed. That lead is recorded in the statement so the next attempt starts from a digest-less reproduction instead of repeating this one. Expiry moves to 2026-09-10, a 14-day review window, and the re-verification is refreshed against this commit: 1335 packages resolved, no openpgp package, and only pbkdf2, scrypt and ocsp linked from x/crypto. Co-authored-by: Cve Ticket Reconciler <cve-ticket-reconciler@stackstate.invalid>
ai-collaboration-app
Bot
changed the title
LouisLotter
reviewed
Aug 28, 2026
| Renewed 2026-08-12. No compatible patch exists: the advisory covers all | ||
| Renewed 2026-08-27. No compatible patch exists: the advisory covers all | ||
| versions (introduced 0, no fixed release) because the openpgp packages are | ||
| permanently unmaintained, so upgrading golang.org/x/crypto cannot clear it. |
There was a problem hiding this comment.
P2 — Enforce the non-reachability claim before suppressing this advisory.
This exception is keyed by image and vulnerability ID only; the evaluator does not match component.purl or paths. As a result, any change that introduces golang.org/x/crypto/openpgp before 2026-09-10 would still be suppressed by this file even though the code would then be affected. The current graph is safe—I independently reproduced the Linux/CGO result of 1,335 packages, no OpenPGP packages, and only pbkdf2, scrypt, and ocsp from x/crypto—but that fact can drift. Please add a fail-closed CI check rejecting ^golang.org/x/crypto/openpgp(/|$) while this exception exists.
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.
The exception lapsed on 2026-08-26, so the gate now reports an expired suppression. This renews it to 2026-09-10 and refreshes the re-verification against this commit (
go list -deps ./cmd/...: 1335 packages, no openpgp package, only pbkdf2, scrypt and ocsp linked from x/crypto).Merging also republishes the commit image, which is what clears the outstanding util-linux and curl advisories on this image —
BCI.dockerfilepins no package versions, so a rebuild picks up util-linux2.40.4-150700.4.18.1and curl8.14.1-150700.7.23.1by itself. No dependency or Dockerfile change was needed, and run 33077013056 confirms it on this branch's current head: the freshly built image produced exactly one in-scope finding, the Go advisory, with no OS-package findings on either architecture.Why two commits: the first deleted the exception, on the theory that the vexhub statement had made it redundant. That run reported the advisory as unmanaged instead, so the second commit restores it and records the reason. Worth knowing before anyone retries deletion: a local rebuild with the same vexhub repository and the same pinned scanner versions did suppress it, and the likely difference is that a locally loaded image carries a RepoDigest — which Trivy uses to build its OCI product purl — while the CI image is built with
load: trueand never pushed.CVE ticket: https://github.com/StackVista/cve-reporter/issues/30. Context on the durable vexhub fix: https://github.com/StackVista/cve-reporter/issues/27. Finding revision
sha256:4f83f6f9a3e6c95535adeadccd4c67d9217427d5f1306b95e415a2be58060617.