addText · When Coalescing Adjacent Text Nodes
Source GCVE Database
Not known to be exploited : upgrade to 0.62.0 when convenient.
Data as of 28 Oct 2026, 01:12 UTC
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.
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
| Fixed in
|
Gogolang.org/x/net/htmlpkg:golang/golang.org/x/net/htmlOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
When coalescing adjacent text nodes in addText and fosterParent, appending to an existing TextNode's Data via string concatenation (n.Data += text) reallocated and copied the accumulated string on every token. Inputs containing many short text runs separated by ignored end tags (such as "a</x>") caused O(n^2) allocations and byte copies. Accumulate coalesced text in per-node byte slices during parsing and materialize Data strings once at the end of parse.