CVE-2026-97045

published 27 Oct 2026 · updated 4 Nov 2026

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

6.1MediumCVSS 6.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 0.62.0.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
golang.org/x/net<0.62.00.62.0

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-97045 severity on Zeptric[![CVE-2026-97045](https://zeptric.io/badge/cve/CVE-2026-97045.svg)](https://zeptric.io/cve/CVE-2026-97045)