Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net (golang.org/x/net golang.org/x/net/html)
At a glance
- Source
- NVD
- EPSS
- EPSS 0.20 % · percentile 10 ()
- State
- PUBLISHED
- Published
- Updated
- Assigner
- Go
- NVD status
- Deferred
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.
References
Advisories
- GO-2026-6866 — Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net
European references
- ENISA EUVD · EUVD-2026-111400
- GCVE · GCVE-0-2026-97045
Affected products
| Product | Versions |
|---|---|
| golang.org/x/net · golang.org/x/net/html | affected 0 < 0.62.0 |
Sources
| Source | Licence |
|---|---|
| CVE List (CVEProject cvelistV5) | CVE Program Terms of Use |
| EPSS (FIRST.org) | FIRST — attribution requested |
| ENISA EUVD | ENISA — reproduction authorised, source acknowledged |
| NVD (NIST) via fkie-cad/nvd-json-data-feeds | Public domain — this product uses data from the NVD API but is not endorsed or certified by the NVD |