CVE-2026-97045
Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net
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.
INFO
Published Date :
Oct. 27, 2026, 10:19 p.m.
Last Modified :
Oct. 27, 2026, 10:19 p.m.
Remotely Exploit :
No
Source :
[email protected]
Solution
- Apply software updates to ensure correct namespace handling.
- Verify integration points for proper HTML namespace resolution.
- Re-parse rendered output to check for namespace consistency.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-97045.
| URL | Resource |
|---|---|
| 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 |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-97045 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-97045
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-97045 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-97045 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by [email protected]
Oct. 27, 2026
Action Type Old Value New Value Added 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. Added Affected New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/97xxx/CVE-2026-97045.json">CVE-2026-97045</a> Added Reference https://go.dev/cl/855121 Added Reference https://go.dev/issue/82622 Added Reference https://groups.google.com/g/golang-announce/c/sqrs2vTx_Xs Added Reference https://pkg.go.dev/vuln/GO-2026-6866