Skip to content

chore(cpworker): bump golang.org/x/net to v0.55.0 in the integration test modules - #319

Merged
timmy21 merged 1 commit into
0.9.xfrom
chore/bump-x-net-0.55
Oct 28, 2026
Merged

timmy21 merged 1 commit into
0.9.xfrom
chore/bump-x-net-0.55

Conversation

@timmy21

@timmy21 timmy21 commented Oct 28, 2026

Copy link
Copy Markdown
Contributor

Clears Dependabot alerts #45 and #46: CVE-2026-25680 / GHSA-5cv4-jp36-h3mw, a denial of service in the x/net/html parser, fixed in golang.org/x/net v0.55.0.

Both alerts are in test-only modules, cpworker/tests/integration and cpworker/tests/integration/helpers/zmq_receiver. They pull x/net indirectly through gopacket/pcapgo → x/net/bpf and never import x/net/html, so the vulnerable code was never built. No shipped component depends on these modules.

Changes:

  • golang.org/x/net v0.38.0 → v0.55.0, and golang.org/x/sys v0.31.0 → v0.45.0 with it.
  • go directive → 1.25.0, required by x/net v0.55.0. It was 1.24.1 in integration and 1.23.0 in zmq_receiver. CI's setup-go already reads 1.25.0 from cpdaemon/go.mod.

Tested on Linux (Go 1.25.10): go vet in both modules, a zmq_receiver build, and ./run_test.sh all all passed.

…test modules

Clears Dependabot alerts #45 and #46 (CVE-2026-25680, GHSA-5cv4-jp36-h3mw,
DoS in the x/net/html parser). Both modules pull x/net only indirectly via
gopacket/pcapgo -> x/net/bpf and never import x/net/html, so the vulnerable
code was not built; the bump is to clear the alerts.

x/net v0.55.0 requires Go 1.25, so the go directive moves to 1.25.0 in
cpworker/tests/integration (from 1.24.1) and helpers/zmq_receiver (from
1.23.0), matching cpdaemon/go.mod which CI's setup-go already uses.
golang.org/x/sys follows to v0.45.0.
@timmy21
timmy21 merged commit 71f75d2 into 0.9.x Oct 28, 2026
1 check passed
@timmy21
timmy21 deleted the chore/bump-x-net-0.55 branch October 28, 2026 09:34
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