fix(deps): bump pacto to v1.4.1 and Go toolchain to 1.26.4 (resolve 3 stdlib CVEs)#100
Merged
Merged
Conversation
Update github.com/trianalab/pacto v1.4.0 -> v1.4.1, which includes the dashboard local-source scan fix (#178: a pacto.yaml under a hidden dir no longer roots local discovery at $HOME and hangs /api/services). Bump the Go build toolchain 1.26.3 -> 1.26.4 (Dockerfile builder + CI/release setup-go) to resolve the three stdlib vulnerabilities reported for the published controller image (all fixed in Go 1.26.4): - CVE-2026-42504 (HIGH) net/textproto MIME header decoding - CVE-2026-27145 (MEDIUM) crypto/x509 VerifyHostname - CVE-2026-42507 (MEDIUM) net/textproto error handling Verified: go build/vet and `make test` pass (controllers at 100% coverage); rebuilding the image with golang:1.26.4 and re-scanning with Trivy reports 0 HIGH/MEDIUM/CRITICAL vulnerabilities (stdlib now v1.26.4).
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
1 participant
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.
Summary
Two related maintenance updates:
github.com/trianalab/pactov1.4.0 → v1.4.1 — the version that includes the dashboard local-source scan fix (pacto#178: apacto.yamlunder a hidden directory no longer roots local discovery at$HOMEand hangs/api/services).All three reported CVEs are in the Go standard library baked into the binary (the image is distroless static — no OS-package CVEs). They are all fixed in Go 1.26.4, so rebuilding with
golang:1.26.4clears them:stdlibnet/textproto (MIME header decode)stdlibcrypto/x509VerifyHostnamestdlibnet/textproto (error handling)Changes
go.mod/go.sum:github.com/trianalab/pactov1.4.0 → v1.4.1 (go mod tidy).Dockerfile: buildergolang:1.26.3→golang:1.26.4(this is what determines the published image's stdlib)..github/workflows/ci.yml(×2) and.github/workflows/auto-release.yml:setup-go1.26.3→1.26.4to keep CI/release consistent with the build toolchain.Related Issues
Picks up TrianaLab/pacto#178 (released in pacto v1.4.1). Addresses the artifacthub security report for
pacto-operator3.2.0.Checklist
make test) — controllers at 100% coveragego vet;make testrunsfmt/vet)<type>: <description>conventionTesting
go build ./...,go vet ./..., andmake test(envtest) all pass.golang:1.26.4and re-scanned with Trivy:pacto-controller:3.2.0, stdlib v1.26.3): 1 HIGH + 2 MEDIUM (the 3 CVEs above).