Repository navigation
Fix x/net HTML vulnerabilities in bundle 0.16.6 - #4
Merged
Merged
Conversation
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.
Docker Machine in the bundle linked
golang.org/x/net v0.60.0, affected by CVE-2026-78661 and CVE-2026-97045. Rebuild bundle 0.16.6 with official x/net v0.62.0 and the dependencies required by its module graph. The existing Go 1.27.3 toolchain, upstream source coordinates, transport/provider implementation and retired Packet policy are unchanged.The two new zero-fuzz patches change only
go.modandgo.sum; source, module, binary and license checks remain exact. The existing full gate and protected-main provenance workflow remain in force.Validation:
The raw product scan retains only the two exact GO-2026-5932 x/crypto v0.58.0 module findings. Neither binary imports OpenPGP or has a reachable package/function trace; the version-bound OpenVEX statement remains the only exception. The protected-main gate and attestation will run before publication.