Skip to main content
CVE-2026-78661VulnerabilityPublished

addText · When Coalescing Adjacent Text Nodes

Source GCVE Database

0
Authoritative record:CVE-2026-78661· Medium

Not known to be exploited : upgrade to 0.62.0 when convenient.

Data as of 28 Oct 2026, 01:12 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Patch
Available – fixed in 0.62.0

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
golang.org/x/netgolang.org/x/net/htmlAffected
  • <0.62.0
Fixed in
  • 0.62.0
Gogolang.org/x/net/htmlpkg:golang/golang.org/x/net/htmlOther threatsAffected
  • <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

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.

References

Community reviews

Loading reviews…