From 6a2025adf4e3195ce12f427c09fe36c72be502d8 Mon Sep 17 00:00:00 2001 From: "SUSE Observability AI (POC)" Date: Thu, 27 Aug 2026 13:04:23 +0000 Subject: [PATCH 1/4] Drop the GO-2026-5932 scan exception 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 --- exceptions/.gitkeep | 0 exceptions/GO-2026-5932.yaml | 34 ---------------------------------- 2 files changed, 34 deletions(-) create mode 100644 exceptions/.gitkeep delete mode 100644 exceptions/GO-2026-5932.yaml diff --git a/exceptions/.gitkeep b/exceptions/.gitkeep new file mode 100644 index 000000000..e69de29bb diff --git a/exceptions/GO-2026-5932.yaml b/exceptions/GO-2026-5932.yaml deleted file mode 100644 index 3214545b7..000000000 --- a/exceptions/GO-2026-5932.yaml +++ /dev/null @@ -1,34 +0,0 @@ -schema_version: "1" -vulnerability: - id: GO-2026-5932 - severity: UNKNOWN -product: - consumer: stackstate-process-agent - image: quay.io/stackstate/stackstate-k8s-process-agent -component: - purl: pkg:golang/golang.org/x/crypto@v0.53.0 - paths: - - opt/stackstate-agent/bin/agent/process-agent -status: accepted_with_compensating_control -reason: unpublished_image_vex_identity_bridge -expires: 2026-08-26 -owner: "@StackVista/observability-team" -upstream_owner: golang -upstream_reference: https://pkg.go.dev/vuln/GO-2026-5932 -statement: | - The affected openpgp and openpgp/clearsign packages are absent from the - process-agent command dependency graph. StackVista/vexhub contains the - reviewed image-scoped not_affected statement, but Grype and Trivy require an - exact image digest or tag to match an image product. This pre-publication - scan uses a newly built commit image whose identity cannot be present in the - VEX hub in advance. Keep this bridge only until the scan pipeline can apply - the reviewed statement to unpublished images without broadening it to every - consumer of golang.org/x/crypto. - - Renewed 2026-08-12. 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. - Absence re-verified against this commit with `go list -deps ./cmd/...`, which - resolves 1329 packages and no openpgp package; the only linked x/crypto - packages are cryptobyte, chacha20, chacha20poly1305, pbkdf2, scrypt and ocsp, - which are also why the indirect module cannot simply be dropped. From 2306309570cb5dc20b448b9e582139ade9732a8f Mon Sep 17 00:00:00 2001 From: "SUSE Observability AI (POC)" Date: Thu, 27 Aug 2026 13:28:20 +0000 Subject: [PATCH 2/4] Renew the GO-2026-5932 exception instead of dropping it MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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 --- exceptions/.gitkeep | 0 exceptions/GO-2026-5932.yaml | 42 ++++++++++++++++++++++++++++++++++++ 2 files changed, 42 insertions(+) delete mode 100644 exceptions/.gitkeep create mode 100644 exceptions/GO-2026-5932.yaml diff --git a/exceptions/.gitkeep b/exceptions/.gitkeep deleted file mode 100644 index e69de29bb..000000000 diff --git a/exceptions/GO-2026-5932.yaml b/exceptions/GO-2026-5932.yaml new file mode 100644 index 000000000..b544dfe26 --- /dev/null +++ b/exceptions/GO-2026-5932.yaml @@ -0,0 +1,42 @@ +schema_version: "1" +vulnerability: + id: GO-2026-5932 + severity: UNKNOWN +product: + consumer: stackstate-process-agent + image: quay.io/stackstate/stackstate-k8s-process-agent +component: + purl: pkg:golang/golang.org/x/crypto@v0.53.0 + paths: + - opt/stackstate-agent/bin/agent/process-agent +status: accepted_with_compensating_control +reason: unpublished_image_vex_identity_bridge +expires: 2026-09-10 +owner: "@StackVista/observability-team" +upstream_owner: golang +upstream_reference: https://pkg.go.dev/vuln/GO-2026-5932 +statement: | + The affected openpgp and openpgp/clearsign packages are absent from the + process-agent command dependency graph. StackVista/vexhub contains the + reviewed image-scoped not_affected statement, but it does not apply to the + pre-publication commit image this pipeline scans. Keep this bridge only until + the scan pipeline can apply the reviewed statement to unpublished images + without broadening it to every consumer of golang.org/x/crypto. + + 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. + Absence re-verified against this commit with `go list -deps ./cmd/...`, which + resolves 1335 packages and no openpgp package; the only linked x/crypto + packages are pbkdf2, scrypt and ocsp, which are also why the indirect module + cannot simply be dropped. + + Deleting this file was tried on this branch and reverted: run 33075037844 + reported the advisory as unmanaged on both architectures, while the containerd + statements in the same vexhub document kept matching. A local rebuild using the + same vexhub repository and the same pinned scanner versions did suppress it, so + the divergence is environmental rather than a change in the statement. One lead + worth checking first: the locally loaded image carries a RepoDigest and Trivy + derives its OCI product purl from that digest, whereas the CI image is built + with load: true and never pushed. Reproduce against a digest-less image before + attempting deletion again. From 447f5b4f5e54975b525d7c68d9cf26feaf3f4556 Mon Sep 17 00:00:00 2001 From: "SUSE Observability AI (POC)" Date: Sat, 29 Aug 2026 10:30:23 +0000 Subject: [PATCH 3/4] Enforce the openpgp non-reachability claim in rake ci 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 --- Rakefile | 7 ++++++- exceptions/GO-2026-5932.yaml | 6 ++++++ scripts/verify-openpgp-absent.sh | 21 +++++++++++++++++++++ 3 files changed, 33 insertions(+), 1 deletion(-) create mode 100755 scripts/verify-openpgp-absent.sh diff --git a/Rakefile b/Rakefile index 77ebe40c5..934e93c3e 100644 --- a/Rakefile +++ b/Rakefile @@ -144,8 +144,13 @@ task :protobuf => [:deps] do sh "protoc proto/agent.proto --proto_path=#{gogo_path} --proto_path=#{sketched_path} -I proto --gogofaster_out model/" end +desc "Fail while golang.org/x/crypto/openpgp is reachable (GO-2026-5932 control)" +task :verify_openpgp_absent do + sh "./scripts/verify-openpgp-absent.sh" +end + desc "Process Agent CI script (imports, vet, etc)" -task :ci => [:deps, :imports, :vet, :lint, :test, :build] +task :ci => [:deps, :imports, :vet, :lint, :test, :build, :verify_openpgp_absent] desc "Process Agent local build" task :local_build => [:prebuild, :build] diff --git a/exceptions/GO-2026-5932.yaml b/exceptions/GO-2026-5932.yaml index b544dfe26..a8a982205 100644 --- a/exceptions/GO-2026-5932.yaml +++ b/exceptions/GO-2026-5932.yaml @@ -31,6 +31,12 @@ statement: | packages are pbkdf2, scrypt and ocsp, which are also why the indirect module cannot simply be dropped. + The compensating control is `scripts/verify-openpgp-absent.sh`, wired into + `rake ci` and so run on each architecture by the build job. The evaluator + matches this exception on image and vulnerability id alone, so without that + check a later import of openpgp would be suppressed by this file rather than + reported. + Deleting this file was tried on this branch and reverted: run 33075037844 reported the advisory as unmanaged on both architectures, while the containerd statements in the same vexhub document kept matching. A local rebuild using the diff --git a/scripts/verify-openpgp-absent.sh b/scripts/verify-openpgp-absent.sh new file mode 100755 index 000000000..8e948434b --- /dev/null +++ b/scripts/verify-openpgp-absent.sh @@ -0,0 +1,21 @@ +#!/usr/bin/env bash +# GO-2026-5932 is suppressed on the claim that openpgp is not linked. The +# scanners match the x/crypto module, not the package, so a change that starts +# importing openpgp would stay suppressed and otherwise reach a release unseen. +set -euo pipefail + +packages="$(go list -deps ./cmd/...)" + +if [ -z "${packages}" ]; then + echo "go list -deps ./cmd/... resolved no packages" >&2 + exit 1 +fi + +if printf '%s\n' "${packages}" | grep -E '^golang\.org/x/crypto/openpgp(/|$)' >&2; then + echo "golang.org/x/crypto/openpgp is reachable from ./cmd/..." >&2 + echo "Withdraw the GO-2026-5932 suppression and address the advisory, or drop the import." >&2 + exit 1 +fi + +printf 'openpgp absent from %s packages reachable from ./cmd/...\n' \ + "$(printf '%s\n' "${packages}" | wc -l)" From ccfe9de936f5ff887d2cbdbd4d48bf5f67e4b538 Mon Sep 17 00:00:00 2001 From: Louis Lotter Date: Sun, 30 Aug 2026 08:17:47 +0200 Subject: [PATCH 4/4] Match OpenPGP guard to the release build graph 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: https://github.com/StackVista/cve-reporter/issues/27 --- Rakefile | 2 +- exceptions/GO-2026-5932.yaml | 10 +++++----- scripts/verify-openpgp-absent.sh | 2 +- 3 files changed, 7 insertions(+), 7 deletions(-) diff --git a/Rakefile b/Rakefile index 934e93c3e..24227318a 100644 --- a/Rakefile +++ b/Rakefile @@ -146,7 +146,7 @@ end desc "Fail while golang.org/x/crypto/openpgp is reachable (GO-2026-5932 control)" task :verify_openpgp_absent do - sh "./scripts/verify-openpgp-absent.sh" + sh "./scripts/verify-openpgp-absent.sh#{get_tag_set(:bpf => true)}" end desc "Process Agent CI script (imports, vet, etc)" diff --git a/exceptions/GO-2026-5932.yaml b/exceptions/GO-2026-5932.yaml index a8a982205..010223487 100644 --- a/exceptions/GO-2026-5932.yaml +++ b/exceptions/GO-2026-5932.yaml @@ -6,7 +6,7 @@ product: consumer: stackstate-process-agent image: quay.io/stackstate/stackstate-k8s-process-agent component: - purl: pkg:golang/golang.org/x/crypto@v0.53.0 + purl: pkg:golang/golang.org/x/crypto@v0.55.0 paths: - opt/stackstate-agent/bin/agent/process-agent status: accepted_with_compensating_control @@ -26,10 +26,10 @@ statement: | 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. - Absence re-verified against this commit with `go list -deps ./cmd/...`, which - resolves 1335 packages and no openpgp package; the only linked x/crypto - packages are pbkdf2, scrypt and ocsp, which are also why the indirect module - cannot simply be dropped. + Absence re-verified against this commit with the same kubelet, kubeapiserver, + linux, cri, containerd and linux_bpf tags used by the release build. The graph + contains no openpgp package; pbkdf2, scrypt and ocsp remain reachable, which + is why the indirect module cannot simply be dropped. The compensating control is `scripts/verify-openpgp-absent.sh`, wired into `rake ci` and so run on each architecture by the build job. The evaluator diff --git a/scripts/verify-openpgp-absent.sh b/scripts/verify-openpgp-absent.sh index 8e948434b..bd62cf20f 100755 --- a/scripts/verify-openpgp-absent.sh +++ b/scripts/verify-openpgp-absent.sh @@ -4,7 +4,7 @@ # importing openpgp would stay suppressed and otherwise reach a release unseen. set -euo pipefail -packages="$(go list -deps ./cmd/...)" +packages="$(GOOS=linux CGO_ENABLED=1 go list -deps "$@" ./cmd/...)" if [ -z "${packages}" ]; then echo "go list -deps ./cmd/... resolved no packages" >&2