Renew the GO-2026-5932 scan exception - #264
Merged
Merged
Conversation
ai-collaboration-app
Bot
changed the title
LouisLotter
reviewed
Aug 28, 2026
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>
The evaluator matches an exception on image and vulnerability id only, so the GO-2026-5932 entry suppresses the advisory regardless of whether the code still satisfies the claim it rests on. Scanners match the x/crypto module rather than the package, so a change that starts importing openpgp would be suppressed by the exception instead of reported by it. scripts/verify-openpgp-absent.sh fails while any package matching ^golang.org/x/crypto/openpgp(/|$) is reachable from ./cmd/..., and also fails when go list errors or resolves nothing, so a broken graph cannot pass as a clean one. It hangs off rake ci rather than a new workflow step, which keeps it on the existing per-architecture build job and lets a developer run the same check locally. It runs unconditionally rather than only while the exception file exists, so renaming that file cannot disable the guard silently. Verified against a stubbed go: a clean graph passes, openpgp and openpgp/clearsign each fail, a go failure and empty output fail, and the near-miss openpgpfoo does not trip the pattern. Co-authored-by: Cve Ticket Reconciler <cve-ticket-reconciler@stackstate.invalid>
Reuse the production BPF tag calculation when checking reachability, and evaluate the Linux graph on developer hosts. Refresh the exception component evidence after the merged x/crypto v0.55 update. Refs: StackVista/cve-reporter#27
LouisLotter
force-pushed
the
cve-go-2026-5932-renew-and-rebuild
branch
from
August 30, 2026 06:18
d152f5c to
ccfe9de
Compare
rb3ckers
approved these changes
Aug 31, 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.
Renews the time-limited GO-2026-5932 exception until 2026-09-10 because the reviewed VEX statement still does not match the unpublished commit image used by this repository's CI.
The branch is rebased after #266 and records x/crypto v0.55.0. A small
rake cicheck evaluates the Linux dependency graph with the release BPF tags and fails if an OpenPGP package becomes reachable.Tracking: https://github.com/StackVista/cve-reporter/issues/27
Validation: the production-tag dependency graph and negative control pass. Full CI is green on amd64 and arm64, including builds, tests, image smoke tests, Trivy/Grype, and signed multi-architecture publication.