Avoid quadratic complexity when coalescing text nodes in html in golang.org/x/net

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
• package golangversion unspecified
• vendor golang.org/x/net golang.org/x/net/htmlversion unspecified

How to fix CVE-2026-78661

• Upgrade

  CVE-2026-78661 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

  • CVE.org · cve.org
  • FIRST EPSS · first.org
  • Go Vulnerability Database · osv.dev
  • OpenSSF OSV / OSV Scanner · osv.dev
  • Snyk Vulnerability Database · security.snyk.io

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Related Odoo Git fixes

Quoted Community commit messages that cite this CVE. Presence of a commit is not proof that every edition or backport includes the fix. Enterprise proprietary diffs are never shown here. Timeline

• Nov 2, 2026 · referenced

  Bump golang.org/x/net to 0.62.0 for cve-2026-78661 and cve-2026-97045

  Merge pull request #143642 from yue9944882/bump-golang-net-cve Bump golang.org/x/net to 0.62.0 for cve-2026-78661 and cve-2026-97045

  https://github.com/kubernetes/kubernetes/commit/512785fb4cdbee732c2b1890709293ac27305252

• Oct 30, 2026 · referenced

  bump golang.org/x/net to 0.62.0 for cve-2026-78661 and cve-2026-97045

  bump golang.org/x/net to 0.62.0 for cve-2026-78661 and cve-2026-97045

  https://github.com/kubernetes/kubernetes/commit/bd872cb03cd0ab35a4ecc65c393317552d47bb3d

• Oct 27, 2026 · referenced

  vendor: golang.org/x/net v0.62.0

  vendor: golang.org/x/net v0.62.0 full diff: https://github.com/golang/net/compare/v0.61.0...v0.62.0 This release addresss the following security issues: - html: avoid quadratic complexity when coalescing text nodes 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") 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. Thanks to Markus Magnuson for reporting this issue. This is CVE-2026-78661 and Go issue https://go.dev/issue/82224. - html: check all ancestor namespace transitions when rendering raw text In childTextNodesAre…

  https://github.com/moby/moby/commit/58131010edd45314f65a6234844926f67d1eebab

Timeline

Detection, updates, and resolution for this record.

1. Oct 27, 2026 · OpenSSF OSV / OSV Scanner

   Detected

   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 ") caused O(n^2) allocations and byte copies. Accumulate coalesced text in per-node byte slices during parsin

2. Oct 27, 2026 · OpenSSF OSV / OSV Scanner

   Fix available

   golang.org/x/net fixed in 0.62.0

3. Oct 27, 2026 · OpenSSF OSV / OSV Scanner

   Fix available

   golang.org/x/net fixed in 0.62.0

4. Oct 27, 2026 · OpenSSF OSV / OSV Scanner

   Updated

   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 ") caused O(n^2) allocations and byte copies. Accumulate coalesced text in per-node byte slices during parsin

5. Oct 27, 2026 · CVE.org

   Updated

   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 ") caused O(n^2) allocations and byte copies. Accumulate coalesced text in per-node byte slices during parsin

Sources

• CVE.orgVulnerability recordCVE-2026-78661

  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 (

  cve.org
• FIRST EPSSExploitation probabilityCVE-2026-78661

  30-day exploitation probability 0.41%

  first.org
• Go Vulnerability DatabasePackage advisoryGO-2026-6860

  Avoid quadratic complexity when coalescing text nodes in html in golang.org/x/net

  osv.dev
• OpenSSF OSV / OSV ScannerPackage advisoryGO-2026-6860

  Avoid quadratic complexity when coalescing text nodes in html in golang.org/x/net

  osv.dev
• Snyk Vulnerability DatabasePackage advisorySNYK-GOLANG-GOLANGORGXNETHTML-21762862

  Denial of Service (DoS)

  security.snyk.io

References

• FIX · go.dev
• REPORT · go.dev
• WEB · groups.google.com
• Reference · pkg.go.dev

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
• Snyk Vulnerability DatabaseOct 31, 2026
• Go Vulnerability DatabaseOct 28, 2026
• OpenSSF OSV / OSV ScannerOct 28, 2026
• CVE.orgOct 28, 2026