What’s Vulnerable › Vulnerabilities

CVE-2026-97045: Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net

• Severity: unknown
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.2% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-10-27 · updated 2026-10-28

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.

Affected products

• Golang.Org/X/Net: before 0.62.0 — fixed in 0.62.0
• golang.org/x/net/html: before 0.62.0 — fixed in 0.62.0

How to fix

Upgrade to a fixed version: Golang.Org/X/Net 0.62.0; golang.org/x/net/html 0.62.0. Check the vendor advisory for mitigations.

References

• https://go.dev/cl/855121
• https://go.dev/issue/82622
• https://groups.google.com/g/golang-announce/c/sqrs2vTx_Xs
• https://pkg.go.dev/vuln/GO-2026-6866

Get alerted when CVE-2026-97045 or the next vulnerability affects your stack