Advisory

GO-2026-6866

Also known as: CVE-2026-97045

Summary

Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net

Details

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.

Severity

Not rated by the source.

Dates

Published
2026-10-27 21:16 UTC
Modified
2026-10-27 21:45 UTC

Affected packages and fixes

golang.org/x/net

Go · All systems

Affected

  • introduced 0, fixed 0.62.0 (semver)

Fixed versions

0.62.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: Go Vulnerability Database · CC BY 4.0

Sources & licences