VDB
Sign up
MEDIUM6.1

GO-2026-6866

Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net

Quick fix

GO-2026-6866 — golang.org/x/net: upgrade to the fixed version with the command below.

go get golang.org/x/net@v0.62.0

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 <mglyph> or <malignmark> fostered under <mtext>), 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.

Are you affected?

Enter the version of the package you're using.

Affected packages

Go/golang.org/x/net
Introduced in: 0Fixed in: 0.62.0
Fixgo get golang.org/x/net@v0.62.0

References