Repository navigation
chore(deps): clear the image's high-severity findings - #277
Conversation
The published chart's Trivy report shows two HIGHs, and both live in the sops binary the image bundles, not in the manager: grpc 1.81.1 (GHSA-hrxh-6v49-42gf) and a Go 1.26.4 stdlib os.Root symlink escape (CVE-2026-39822). sops v3.13.3 is built with go1.26.5 and grpc v1.82.1, so the bump retires both plus the crypto/tls MEDIUM alongside them. The manager's own MEDIUM was cel-go 0.28.1 (GHSA-gcjh-h69q-9w9g); `go get -u ./...` carries it to 0.30.0 and moves the rest of the module graph with it. The three pinned base-image digests already resolve to the current tags and Go 1.26.5 is the newest release, so nothing there needed to move. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
📝 WalkthroughWalkthroughThe Docker build updates SOPS to v3.13.3. The Go module manifest updates direct dependencies and multiple indirect dependency groups, including OpenTelemetry, Kubernetes, OpenAPI, and related modules. ChangesVersion updates
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Dockerfile`:
- Line 56: Update the SOPS download flow around the SOPS_VERSION build argument
to verify the architecture-specific binary before chmod and packaging. Use
SOPS’s signed checksums/provenance artifact or an equivalent SHA-256 check,
ensure the selected architecture’s checksum matches the downloaded binary, and
fail the build on mismatch.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: c27eb403-5cdc-4844-92c8-aec4f5b27e72
⛔ Files ignored due to path filters (1)
go.sumis excluded by!**/*.sum
📒 Files selected for processing (2)
Dockerfilego.mod
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
The published chart's Artifacthub security report flags two HIGHs against
ghcr.io/configbutler/gitops-reverser:0.39.2. Both are in thesopsbinary the image bundles, not in the manager:sopsos.Rootsymlink escape)sopscrypto/tls)sopsmanagerSOPS_VERSIONmoves to v3.13.3, whichgo version -mconfirms is built with go1.26.5 and grpc v1.82.1 — that retires all three sops findings.go get -u ./... && go mod tidytakes cel-go to 0.30.0, retiring the manager's, and carries ~35 other modules with it (k8s.io/apiextensions-apiserver 0.36.1→0.36.3, otel exporters →1.44.0, go-openapi/swag →0.27.3, x/tools →0.48.0). The k8s.io core libraries were already at the newest 0.36.3.Checked and left alone because they are already current: all three pinned base-image digests (
golang:1.26.5,alpine:3.24,gcr.io/distroless/static:debug) resolve to exactly the digests in the Dockerfile, and Go 1.26.5 is the latest release.Out of scope: the devcontainer's tool pins. They are dev-only, never reach the published image, and validating a bump means rebuilding the container this work runs inside.
Validation:
task fmt,generate,manifests,vet,lint,test(77.9%, baseline 78.0%) andtask test-e2e(69 of 91 specs, 0 failed) all pass.🤖 Generated with Claude Code
Summary by CodeRabbit