Vulnerability · CVE-2026-97045
Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net
Published Oct 27, 2026 · catalog updated Oct 27, 2026 · Check all ancestor namespace
Last checked Nov 5, 2026. A connected source was read within the last 7 days.
Check if you run it
No confirmed exploitation is on record for CVE-2026-97045. EPSS is 0.27%. Act only if a listed version of Check all ancestor namespace is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (Check all ancestor namespace).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
Same product and reporting
- CVE-2026-78661 · High
- CVE-2025-47911 · Medium
- CVE-2025-58190 · Medium
- CVE-2025-22872 · Medium
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.27%
- Remediation
- Not established
- Affected products
- Go golang.org/x/net · vendor golang.org/x/net golang.org/x/net/html
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 or fostered under ), 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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- Go golang.org/x/net0 → 0.62.0
- vendor golang.org/x/net golang.org/x/net/htmlversion unspecified
How to fix CVE-2026-97045
Upgrade
CVE-2026-97045 lists a fix boundary at 0.62.0. Compare the installed build with that boundary before you change production.
Version check
Fixed in 0.62.0
Advisory
Open the cve_org record and follow its fix.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-97045. EPSS is 0.27%. Act only if a listed version of Check all ancestor namespace is installed.
Which versions are affected?
Compare what you have installed with 0 → 0.62.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 0.27%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Oct 27, 2026 · OpenSSF OSV / OSV Scanner
Detected
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 or fostered under ), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the rendered out
Oct 27, 2026 · OpenSSF OSV / OSV Scanner
Fix available
golang.org/x/net fixed in 0.62.0
Oct 27, 2026 · OpenSSF OSV / OSV Scanner
Fix available
golang.org/x/net fixed in 0.62.0
Oct 27, 2026 · OpenSSF OSV / OSV Scanner
Updated
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 or fostered under ), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the rendered out
Sources
- CVE.orgVulnerability recordCVE-2026-97045
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 or fos
cve.org - FIRST EPSSExploitation probabilityCVE-2026-97045
30-day exploitation probability 0.27%
first.org - Go Vulnerability DatabasePackage advisoryGO-2026-6866
Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net
osv.dev - OpenSSF OSV / OSV ScannerPackage advisoryGO-2026-6866
Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net
osv.dev
References
Freshness
Last verified in this catalog Nov 5, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- FIRST EPSSNov 5, 2026
- Go Vulnerability DatabaseOct 28, 2026
- OpenSSF OSV / OSV ScannerOct 28, 2026
- CVE.orgOct 28, 2026