Skip to content

fix: remediate GO-2026-5942 in extras/dagger - #3313

Open
chainloop-platform[bot] wants to merge 1 commit into
mainfrom
chainloop/fix-go-2026-5942-golang-org-x-net-20260729-002718
Open

fix: remediate GO-2026-5942 in extras/dagger#3313
chainloop-platform[bot] wants to merge 1 commit into
mainfrom
chainloop/fix-go-2026-5942-golang-org-x-net-20260729-002718

Conversation

@chainloop-platform

@chainloop-platform chainloop-platform Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Summary

Updated the auxiliary extras/dagger Go module to use the fixed golang.org/x/net release that resolves GO-2026-5942. The module resolver also advanced golang.org/x/sys to the matching indirect version required by the updated dependency graph.

Vulnerability Fixed

GO-2026-5942-golang.org/x/net (HIGH): Parsing an invalid SVCB or HTTPS RR can panic when the size of a parameter value overflows the message buffer.

Changes Made

  • Bumped extras/dagger/go.mod from golang.org/x/net v0.55.0 to v0.56.0, the first fixed release identified by the assessment hint and module version check.
  • Refreshed extras/dagger/go.sum with the new golang.org/x/net checksums and the resolver-required golang.org/x/sys v0.46.0 checksums.

Verification

Ran syft dir:. -o json | grype -q --only-fixed -o json from the repository root and checked the resulting matches for GO-2026-5942-golang.org/x/net. Outcome: resolved — Grype no longer reports the target advisory in the patched source tree.

Risk Assessment

View the risk assessment in Chainloop

Review in cubic

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.

0 participants