CVE-2026-97045
Severity not reportedIn childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once an HTML integration point was found.
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.
Affected products
Not reported by the source (unknown — not "none").
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://go.dev/cl/855121 security@golang.org
- https://go.dev/issue/82622 security@golang.org
- https://groups.google.com/g/golang-announce/c/sqrs2vTx_Xs security@golang.org
- https://pkg.go.dev/vuln/GO-2026-6866 security@golang.org
