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.
Fix
Nothing published yet: no patch, vendor advisory or mitigation reference on NVD, no vendor advisory in the News for this CVE, not in CISA's KEV, no fixed package version. BaselineWatch does not guess at one.
Change history 4
- StatusPublished → DeferredNVD modified 2026-10-28 15:24
- StatusReceived → PublishedNVD modified 2026-10-27 21:38
- StatusPublished → ReceivedNVD modified 2026-10-27 22:19
- First seenunscored · golang.org/x/netNVD modified 2026-10-27 21:38
Affected (CPE criteria) 0
NVD has not attached CPE configurations yet.