CVE-2026-78661

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

Published Oct 27, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The vulnerability resides in golang.org/x/net's HTML parsing package. When the parser merges adjacent text nodes, it appends to existing TextNode data with repeated string concatenation (n.Data += text). On each token this reallocates and copies the entire accumulated string, resulting in quadratic time and space consumption. Crafting input with many short text fragments separated by ignored end tags triggers O(n²) allocations and copies, leading to excessive CPU and memory usage.

Affected Systems

Any Go program that imports golang.org/x/net/html for parsing or rendering HTML may be impacted. The CVE does not specify a particular version; therefore, all releases containing the unpatched logic are susceptible.

Risk and Exploitability

The CVSS score is 7.5, the EPSS score is less than 1%, and the vulnerability is not listed in the CISA KEV catalog. The quadratic processing can be exploited by feeding large amounts of text to the parser. An attacker that can supply user‑controlled HTML could trigger O(n²) allocations and excessive CPU and memory usage, potentially causing service degradation or a crash. The risk is considered high given the potential for resource exhaustion.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update golang.org/x/net to a version that implements byte‑slice accumulation for text nodes
  • If an upgrade is not immediately possible, enforce a maximum input size or reject requests containing an unusually large number of text fragments before they reach the parser
  • Monitor CPU and memory usage of processes that parse HTML and apply throttling or canary deployment to detect resource exhaustion incidents

Generated by OpenCVE AI on November 4, 2026 at 19:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Weaknesses CWE-407
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Golang
Golang net
Vendors & Products Golang
Golang net
Type Values Removed Values Added
Weaknesses CWE-770
Type Values Removed Values Added
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.
Title Avoid quadratic complexity when coalescing text nodes in html in golang.org/x/net
References
Weaknesses
  • CWE-407

    Inefficient Algorithmic Complexity

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
Go
Published
Updated
Nov 4, 2026, 4:40 PM
Reserved
Aug 24, 2026, 11:36 PM
Status
Deferred
Published
Oct 27, 2026, 10:18 PM
Modified
Nov 4, 2026, 5:17 PM