Answer in brief
CVE-2026-97045 records a Unknown severity vulnerability in Check all ancestor namespace transitions when rendering raw text in html in golang.org/x/net. The current sources do not mark it as known exploited. The current feed maps golang.org/x/net (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps golang.org/x/net (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| golang.org/x/netgo | >=0 <0.62.0 | 0.62.0 |
Published upstream
Oct 27, 2026
Evidence: source:osv:source_dates:source-dates:recordSource modified
Oct 27, 2026
Evidence: source:osv:source_dates:source-dates:recordFirst seen by HOL
Oct 27, 2026
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.
Quoted source text, attributed separately from HOL analysis.