Repository navigation
fix(deps): remediate GO-2026-5932 with upstream OpenPGP module split - #125
Merged
Merged
Conversation
LouisLotter
approved these changes
Nov 6, 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.
Release artifact scans still report GO-2026-5932 for
golang.org/x/crypto v0.58.0. Update the indirect requirement tov0.58.1-0.20261009181718-2f1f834330b2, the exact fixed revision listed in the Go vulnerability database. This upstream commit separates the unmaintained OpenPGP packages into their own module. The backup CLI imports onlyx/crypto/sha3; the retained module files are byte-for-byte identical to v0.58.0, and the dependency still requires Go 1.26.0. The repository remains on Go 1.26.10.Reuse the already merged Renovate fixes #123 (Brotli 1.2.7, CVE-2026-111497) and #124 (compress 1.20.2, CVE-2026-116591). Their combined main CI passed all five release targets; downloaded security evidence has no Trivy vulnerability or secret findings and only GO-2026-5932 in Grype.
Related canonical ticket: https://github.com/StackVista/cve-reporter/issues/114 (supervisor owns delivery verification and ticket updates).
Scan provenance: https://github.com/StackVista/cve-reporter/actions/runs/42183453045, attempt 1, aggregate
sha256:18a7dc3341e07a33facd41c5f3dac16aa01a4c5b0d792e72f111fa126fe8ff5d.Validation passed at signed head
8062fe34b954f39e900dee21f658531c4d66644d:go mod verify,go test ./..., configured golangci-lint v2.15.0 (zero issues), build, and CLI help/version smoke checks passed. Local Grype found zero fixable vulnerabilities with the 2026-11-06 database.restore→portforward,scale,scripts;scale→restorelock); this dependency-only change adds none.Ready for supervisor-assigned independent review.
After independent review and normal protected merge, publish the normal
v0.11.3release through the existing tag-triggered workflow. GitHub/S3 archive names remain consumable by container-toolsSTS_BACKUP_VERSION,STS_BACKUP_SHA256_AMD64, andSTS_BACKUP_SHA256_ARM64; consumer adoption belongs to the supervisor. The full v0.11.2-to-main release range contains merged dependency (AWS, ClickHouse, Kubernetes and compression) and CI/Renovate updates, with no application-code changes. Publication has not occurred.