–
Not scored
CVE-2026-97045
Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net
golang.org/x/net/htmlAffectedgolang.org/x/net/html
FixUpdate to 0.62.0 or newer
PublishedOct 27, 21:38 · Go
ScoredNot yet
Exploit code publicNone known · checked 21:18 UTC
ExploitedNone known · CISA KEV checked 22:06 UTC
What we know
No known exploitation. CISA KEV, checked 22:06 UTC.
No public exploit code known. Exploit-DB, Metasploit, Nuclei, checked 21:18 UTC.
No severity score yet.
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 Go
Affected and fixed versions
ProductAffectedFixed ingolang.org/x/net/htmlbefore 0.62.00.62.0
Exploit code
Exploit-DBnone knownMetasploitnone knownNucleinone known