Skip to content

govulncheck red on crux main: GO-2026-6617/6612/6611/6603 in src/crux golang.org/x/net v0.59.0 #14781

Closed

Description

@clubanderson

govulncheck (known vulnerabilities) is red on hivecommons/crux main HEAD, which marks every crux PR (e.g. hivecommons/crux#22) base-branch-red. crux Go code is synced from src/crux/ here, so the fix must land on v5.

Failing run: https://github.com/hivecommons/crux/actions/runs/40607992333/job/122552204826

Findings, all in golang.org/x/net@v0.59.0 (src/crux/go.mod):

  • GO-2026-6617 (fixed in v0.60.0)
  • GO-2026-6612 (fixed in v0.60.0)
  • GO-2026-6611 (fixed in v0.60.0)
  • GO-2026-6603 (fixed in v0.60.0)

Fix: bump golang.org/x/net to v0.62.0 in src/crux (matches #14731 for the root module) and go mod tidy.

Tracking on the crux side: hivecommons/crux#26

Activity

  1. hivecommons-hive commented on Oct 28, 2026

    @hivecommons-hive
    Contributor

    🔒 Claimed by @thatguywob (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.

  2. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Oct 28, 2026
  3. thatguywob commented on Oct 28, 2026

    @thatguywob
    Contributor

    PR #14782 (#14782) already covers the full requested fix and is open, ready for review, against v5. I inspected its diff: it upgrades src/crux/go.mod from golang.org/x/net v0.59.0 to v0.62.0, updates the required golang.org/x/sys version and src/crux/go.sum, and adds a security changelog fragment. Its body already includes Fixes #14781.

    No additional implementation is needed alongside that PR. The fix is awaiting merge; it is not yet on v5.

    — hive: backend=codex


    🐝 Hive Agent: contributor | SHA: 70716fdce

  4. hivecommons-hive commented on Oct 28, 2026

    @hivecommons-hive
    Contributor

    🔓 Claim by @thatguywob released (lease revoked).

  5. github-actions commented on Oct 28, 2026

    @github-actions
    Contributor

    @clubanderson this issue was closed by @hivecommons-hive[bot] as completed.

    If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.

    If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions