VulnerabilityPublished 28 Oct 2026

CVE-2026-97045: In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor

Source GCVE Database

Authoritative record:CVE-2026-97045· High

Not known to be exploited : upgrade to 0.62.0 soon.

Data as of 28 Oct 2026, 01:12 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in 0.62.0

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-vwcj-r8v9-p53f

What to do

Upgrade golang.org/x/net/html to 0.62.0.

Affected software

Product	Affected	Fixed in
golang.org/x/netgolang.org/x/net/html	Affected <0.62.0	Fixed in 0.62.0
Gogolang.org/x/net/html`pkg:golang/golang.org/x/net/html`Other threats	Affected <0.62.0	Fixed in 0.62.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…