Repository navigation
Conversation
Clears the only actionable finding out of the 48 open code-scanning alerts.
golang.org/x/net v0.61.0 -> v0.62.0 (indirect)
v0.61.0 arrived with the weekly group bump and carries two advisories in
`x/net/html`, both fixed in 0.62.0:
CVE-2026-78661 coalescing adjacent text nodes in addText/fosterParent
CVE-2026-97045 childTextNodesAreLiteral stops walking up the tree
Neither is reachable here: `go list -deps ./...` shows `golang.org/x/net/html`
is not in the build graph at all, which is also why `govulncheck` reported 0
affected both before and after. Trivy flags the module version rather than the
imported package, so the alerts were real as reported and are worth clearing
rather than dismissing -- a one-line indirect bump is cheaper than carrying two
permanent exceptions, and the next person reading the alert list should not have
to re-derive that the package is unused.
Verified: `go build ./...`, `go vet ./...` and `go test ./...` all pass (0
failures); `govulncheck` 0 affected; `trivy fs` on `server/go.mod` drops from 3
findings to 1.
That remaining one is GO-2026-5932 -- `golang.org/x/crypto/openpgp` is
unmaintained -- and it is deliberately left alone in both modules. Its only
"fix" is the pseudo-version 0.58.1-0.20261009181718-2f1f834330b2, and trading a
tagged release for an untagged commit is a worse trade than the finding: the
openpgp package is likewise absent from both build graphs.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
chore(deps): bump x/net to 0.62.0 for the two html-parser advisories
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Promotes
developtomain. One commit, two files —server/go.modandserver/go.sum.Why it needs to reach main
Code-scanning alerts are computed against the default branch. #312 put the fix on
develop, so alerts #178 (CVE-2026-78661) and #179 (CVE-2026-97045) are still open onmain— they are the only two open code-scanning alerts left, and this merge is what closes them.Both are advisories in
x/net/html. Neither is reachable:go list -deps ./...showsgolang.org/x/net/htmlis not in the build graph, which is whygovulncheckreported 0 affected before and after. Trivy flags the module version rather than the imported package.Verification
Carried over from #312, where all 8 checks passed:
go build ./...,go vet ./...,go test ./...— 0 failures.govulncheck— 0 affected, both modules.trivy fsonserver/go.mod— 3 findings → 1. The one left isGO-2026-5932(x/crypto/openpgpunmaintained), dismissed as won't-fix: its only published fix is a pseudo-version, and that package is absent from both build graphs too.What this does not do
Merging to
mainbuilds and publishes nothing — the release workflows fire on tags. This bump ships with the next server tag, which needs its own image CVE gate at that time.🤖 Generated with Claude Code