CVE-2026-97045
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.
- Status
- Deferred - security@golang.org
- Published
- 2026-10-27
- Last modified
- 2026-10-28
Affected products
References
- https://go.dev/cl/855121
- https://go.dev/issue/82622
- https://groups.google.com/g/golang-announce/c/sqrs2vTx_Xs
- https://pkg.go.dev/vuln/GO-2026-6866