Skip to content

fix: remediate GO-2026-5026 in extras/dagger#3275

Closed
chainloop-development[bot] wants to merge 1 commit into
mainfrom
chainloop/fix-go-2026-5026-golang-org-x-net-20260708-141835
Closed

fix: remediate GO-2026-5026 in extras/dagger#3275
chainloop-development[bot] wants to merge 1 commit into
mainfrom
chainloop/fix-go-2026-5026-golang-org-x-net-20260708-141835

Conversation

@chainloop-development

@chainloop-development chainloop-development Bot commented Jul 8, 2026

Copy link
Copy Markdown

Summary

Updated the optional extras/dagger module to resolve golang.org/x/net to v0.55.0, the first fixed release for this advisory. Because v0.55.0 requires Go 1.25, the submodule's Go version and companion x/* indirect modules were raised by Go's module resolver.

Vulnerability Fixed

GO-2026-5026-golang.org/x/net (HIGH): the idna package accepted certain Punycode labels that decode to ASCII-only labels, which can bypass hostname-based privilege checks.

Changes Made

  • Bumped extras/dagger/go.mod from golang.org/x/net v0.44.0 to v0.55.0, the lowest fixed release in the assessment hint.
  • Accepted the accompanying indirect upgrades to golang.org/x/sync, golang.org/x/sys, and golang.org/x/text, plus the extras/dagger go directive bump to 1.25.0, because golang.org/x/net v0.55.0 requires Go 1.25.
  • Refreshed extras/dagger/go.sum to record the patched module graph.

Verification

Ran syft dir:. -o cyclonedx-json=<tempfile> && grype sbom:<tempfile> --only-fixed -o json from the repository root. Outcome: resolved — GO-2026-5026-golang.org/x/net and golang.org/x/net no longer appear in the scan results after the bump. The scan still reports unrelated fixed vulnerabilities in other extras/dagger dependencies.

Risk Assessment

View the risk assessment in Chainloop

Review in cubic

migmartri added a commit to migmartri/chainloop that referenced this pull request Jul 9, 2026
Combined upgrade of the extras/dagger module dependencies to resolve
all four open security advisories in a single change, since the
individual bot PRs (chainloop-dev#3273, chainloop-dev#3274, chainloop-dev#3275, chainloop-dev#3276) conflict with each
other by modifying the same go.mod lines.

Advisories resolved:
- GHSA-p77j-4mvh-x3m3 (CRITICAL): gRPC-Go authorization bypass via
  missing leading slash in :path. Fixed by grpc v1.80.0 (>= v1.79.3).
- GHSA-mh2q-q3fh-2475 (HIGH): OpenTelemetry-Go baggage header DoS.
  Fixed by OTel v1.43.0 (>= v1.41.0).
- GHSA-hfvc-g4fc-pqhx (HIGH): OpenTelemetry-Go BSD kenv PATH hijack.
  Fixed by OTel SDK v1.43.0.
- GO-2026-5026 (HIGH): golang.org/x/net idna Punycode bypass.
  Fixed by x/net v0.55.0.

Verification performed:
- dagger develop (codegen) succeeds
- go build ./... compiles
- go vet ./... passes
- golangci-lint run: 0 issues
- go mod verify: all modules verified
- dagger call loads and instantiates the module
- with-instance function executes
- init function executes (fails at auth layer, not code)
- init --enterprise pulls enterprise image and executes

🤖 _Posted by Maximus bot on behalf of @migmartri_
migmartri added a commit to migmartri/chainloop that referenced this pull request Jul 9, 2026
Combined upgrade of the extras/dagger module dependencies to resolve
all four open security advisories in a single change, since the
individual bot PRs (chainloop-dev#3273, chainloop-dev#3274, chainloop-dev#3275, chainloop-dev#3276) conflict with each
other by modifying the same go.mod lines.

Advisories resolved:
- GHSA-p77j-4mvh-x3m3 (CRITICAL): gRPC-Go authorization bypass via
  missing leading slash in :path. Fixed by grpc v1.80.0 (>= v1.79.3).
- GHSA-mh2q-q3fh-2475 (HIGH): OpenTelemetry-Go baggage header DoS.
  Fixed by OTel v1.43.0 (>= v1.41.0).
- GHSA-hfvc-g4fc-pqhx (HIGH): OpenTelemetry-Go BSD kenv PATH hijack.
  Fixed by OTel SDK v1.43.0.
- GO-2026-5026 (HIGH): golang.org/x/net idna Punycode bypass.
  Fixed by x/net v0.55.0.

Assisted-by: Claude Code
Signed-off-by: Miguel Martinez <migmartri@gmail.com>
Signed-off-by: Miguel Martinez Trivino <miguel@chainloop.dev>
@migmartri migmartri closed this Jul 9, 2026
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