Repository navigation
chore(deps): update module golang.org/x/net to v0.62.0 [security] (release-2.1) - #3938
renovate[bot] wants to merge 1 commit into
Conversation
|
✅ PR images built and pushed successfully! Images are available for testing (expires in 7 days):
|
|
/hold — waiting on 2.1.0 tag to be pushed across all repos. |
2356f20 to
c655b15
Compare
|
✅ PR images built and pushed successfully! Images are available for testing (expires in 7 days):
|
c655b15 to
5c9d5fd
Compare
|
✅ PR images built and pushed successfully! Images are available for testing (expires in 7 days):
|
5c9d5fd to
6d55daa
Compare
|
✅ PR images built and pushed successfully! Images are available for testing (expires in 7 days):
|
6d55daa to
f7aefb6
Compare
|
✅ PR images built and pushed successfully! Images are available for testing (expires in 7 days):
|
f7aefb6 to
95b3968
Compare
|
✅ PR images built and pushed successfully! Images are available for testing (expires in 7 days):
|
95b3968 to
f294354
Compare
|
✅ PR images built and pushed successfully! Images are available for testing (expires in 7 days):
|
f294354 to
a271dff
Compare
|
✅ PR images built and pushed successfully! Images are available for testing (expires in 7 days):
|
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
a271dff to
40c68b1
Compare
|
|
✅ PR images built and pushed successfully! Images are available for testing (expires in 7 days):
|



This PR contains the following updates:
v0.61.0→v0.62.0Avoid quadratic complexity when coalescing text nodes in html in golang.org/x/net
CVE-2026-78661 / GO-2026-6860
More information
Details
When coalescing adjacent text nodes in addText and fosterParent, appending to an existing TextNode's Data via string concatenation (n.Data += text) reallocated and copied the accumulated string on every token. Inputs containing many short text runs separated by ignored end tags (such as "a") caused O(n^2) allocations and byte copies.
Accumulate coalesced text in per-node byte slices during parsing and materialize Data strings once at the end of parse.
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net
CVE-2026-97045 / GO-2026-6866
More information
Details
In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once an HTML integration point was found. However, that integration point may itself be a descendant of an element that was foster-parented into a foreign namespace (such as or fostered under ), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the rendered output.
Continue walking the full ancestor chain and verify that every transition from a non-empty namespace occurs at an HTML integration point before emitting literal text.
Severity
Unknown
References
This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.