Skip to content

chore(deps): bump go-jose, sigstore, x/net and CI tools - #156

Merged
leet-c1 merged 1 commit into
mainfrom
chore/deps-bump
Nov 3, 2026
Merged

leet-c1 merged 1 commit into
mainfrom
chore/deps-bump

Conversation

@leet-c1

@leet-c1 leet-c1 commented Nov 3, 2026

Copy link
Copy Markdown
Contributor

Bumps every outdated direct dependency and CI tool pin, and the vulnerable indirect x/net. Supersedes #155.

Go modules

Module From To Why
go-jose/v4 v4.1.5 v4.1.8 v4.1.6 fixes GHSA-mgcc-cww5-fp2q. v4.1.7 fixes GHSA-r39w-98wm-9pp6, GHSA-27pc-rm86-68pq, GHSA-p9j4-2j95-j4rv, GHSA-v6h2-qj3f-2h6v and GHSA-c67m-wr4h-2ccg. v4.1.8 only adds ML-DSA.
sigstore/sigstore v1.11.0 v1.11.2 outdated
sigstore/sigstore-go v1.3.0 v1.4.0 outdated
go.yaml.in/yaml/v3 v3.0.5 v3.0.6 outdated
golang.org/x/mod v0.41.0 v0.42.0 outdated
golang.org/x/net (indirect) v0.60.0 v0.62.0 GO-2026-6860, GO-2026-6866

The other indirect bumps come from go mod tidy.

The five v4.1.7 jose advisories aren't in the Go vulnerability database yet, so govulncheck doesn't flag them at v4.1.6.

CI pins (ci.yaml)

golangci-lint v2.14.0 → v2.15.0, govulncheck v1.8.0 → v1.9.0, gosec v2.29.0 → v2.30.0. The uses: action pins and gitleaks were already on their latest releases.

Risk

  • jose: c1i only parses an Ed25519 JWK and signs an EdDSA client assertion (internal/tokensource). The RSA modulus cap, the stricter x5c and header parsing, and the recipient and signature limits don't touch that path.
  • sigstore-go v1.4.0: the default TUF fetcher changed, but c1i injects its own. No verification-policy defaults changed for the APIs internal/selfupdate calls.

Verification

  • go build, go vet and go test -count=1 -shuffle=on ./... pass.
  • golangci-lint v2.15.0 and gosec v2.30.0 (run with CI's flags) pass.
  • go mod tidy leaves no diff, and gitleaks finds nothing.
  • govulncheck v1.9.0 passes for linux, darwin and windows.
  • Live client-credentials token mint, auth whoami and users list all succeed against a test tenant.
  • TestVerifyManifestReal verifies a real release's Sigstore signature after fetching the trust root live.

Not fixed

GO-2026-5932 (x/crypto/openpgp) is still open. c1i doesn't import that package, govulncheck reports it as not called, and the fix isn't in a tagged x/crypto release yet. It should go in when x/crypto tags a release with the fix.

🤖 Generated with Claude Code

Direct modules:
- go-jose/v4 v4.1.5 -> v4.1.8: v4.1.6 and v4.1.7 fix six GHSA
  advisories (RSA modulus cap, recipient/signature limits, header
  presence checks, among others). v4.1.8 only adds ML-DSA.
- sigstore v1.11.0 -> v1.11.2, sigstore-go v1.3.0 -> v1.4.0
- go.yaml.in/yaml/v3 v3.0.5 -> v3.0.6, x/mod v0.41.0 -> v0.42.0

Indirect: x/net v0.62.0 fixes GO-2026-6860 and GO-2026-6866; the rest
follow from the above via go mod tidy.

CI: golangci-lint v2.15.0, govulncheck v1.9.0, gosec v2.30.0.

GO-2026-5932 (x/crypto/openpgp, not imported here) stays open: its fix
is not in a tagged x/crypto release yet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leet-c1
leet-c1 merged commit 3230c8a into main Nov 3, 2026
2 checks passed
@leet-c1
leet-c1 deleted the chore/deps-bump branch November 4, 2026 05:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant