Go x/net/html namespace parsing mismatch in childTextNodesAreLiteral
golang.org/x/net/html
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| golang.org/x/net golang.org/x/net/html |
| No fix yet |
Original description
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.
From the CVE record · Go