Skip to content

fix(deps): bump golang.org/x/net to v0.56.0, clear GO-2026-5942 - #208

Open
acamarata wants to merge 1 commit into
mainfrom
fix/xnet-dnsmessage-panic
Open

fix(deps): bump golang.org/x/net to v0.56.0, clear GO-2026-5942#208
acamarata wants to merge 1 commit into
mainfrom
fix/xnet-dnsmessage-panic

Conversation

@acamarata

Copy link
Copy Markdown
Collaborator

Summary

Test plan

  • go build -mod=vendor ./... — clean
  • CGO_ENABLED=0 go test -mod=vendor ./... — 98/98 packages pass, 0 failures
  • go run golang.org/x/vuln/cmd/govulncheck@latest ./... (go1.26.6) — 0 vulnerabilities
  • CI: Go Vulnerability Check green on main
  • CI: Nightly Security Audit (govulncheck) green on main

The Nightly Security Audit re-run after #207 landed flagged a newly
published govulncheck finding (GO-2026-5942, CVE-2026-46600, added to
the vuln DB 2026-08-14 — after #207's local scan): parsing an invalid
SVCB/HTTPS DNS resource record can panic when a parameter value
overflows the message buffer.

The stdlib half of this CVE (net.LookupCNAME et al.) is already fixed
by the go1.26.6 toolchain bump from #207. The remaining reachable path
is golang.org/x/net/dns/dnsmessage, pulled in transitively via grpc;
bumped v0.55.0 -> v0.56.0 (fixed version) and re-vendored.

Verified locally with go1.26.6: govulncheck ./... reports 0 vulnerabilities,
go build -mod=vendor ./... succeeds, go test -mod=vendor ./... passes all
98 packages.
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