CVE-2026-78661: Avoid quadratic complexity when coalescing text nodes in html in golang.org/x/net

Published Oct 27, 2026
·
Updated

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

Other sources

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.

— MITRE

Affected Software

88 affected componentsFixes available
go/golang.org/x/net
debian/golang-golang-x-net<=1:0.7.0+dfsg-1, <=1:0.27.0-2
1:0.62.0-1
debian/golang-golang-x-net*
debian/golang-golang-x-net*
debian/golang-golang-x-net<1:0.62.0-1
1:0.62.0-1
ubuntu/golang-1.10*
ubuntu/golang-1.10*
ubuntu/golang-1.6*
ubuntu/golang-golang-x-net-dev*
ubuntu/juju-core*
ubuntu/lxd*
ubuntu/containerd*
ubuntu/golang-1.13*
ubuntu/golang-1.18*
ubuntu/google-guest-agent*
ubuntu/google-osconfig-agent*
ubuntu/golang-1.10*
ubuntu/lxd*
ubuntu/containerd*
ubuntu/golang-1.13*
ubuntu/golang-1.16*
ubuntu/golang-1.18*
ubuntu/golang-1.8*
ubuntu/golang-golang-x-net-dev*
ubuntu/google-guest-agent*
ubuntu/google-osconfig-agent*
ubuntu/adsys*
ubuntu/containerd*
ubuntu/golang-1.13*
ubuntu/google-guest-agent*
ubuntu/golang-1.16*
ubuntu/golang-1.18*
ubuntu/golang-1.22*
ubuntu/golang-golang-x-net-dev*
ubuntu/google-osconfig-agent*
ubuntu/lxd*
ubuntu/adsys*
ubuntu/containerd*
ubuntu/golang-1.17*
ubuntu/golang-1.22*
ubuntu/golang-1.24*
ubuntu/google-guest-agent*
ubuntu/google-osconfig-agent*
ubuntu/golang-1.13*
ubuntu/golang-golang-x-net*
ubuntu/adsys*
ubuntu/golang-1.21*
ubuntu/golang-1.22*
ubuntu/golang-1.24*
ubuntu/google-guest-agent*
ubuntu/google-osconfig-agent*
ubuntu/containerd*
ubuntu/golang-golang-x-net*
ubuntu/adsys*
ubuntu/containerd*
ubuntu/golang-1.26*
ubuntu/golang-golang-x-net*
ubuntu/google-guest-agent*
ubuntu/google-osconfig-agent*
ubuntu/adsys*
ubuntu/golang-1.23*
ubuntu/golang-1.24*
ubuntu/golang-golang-x-net*
ubuntu/google-guest-agent*
ubuntu/google-osconfig-agent*
ubuntu/containerd*
All of the following
azurelinux/dasel<2.8.1-6
2.8.1-6
Microsoft Azure Linux=3.0
All of the following
azurelinux/cri-tools<1.32.0-11
1.32.0-11
Microsoft Azure Linux=3.0
All of the following
azurelinux/gh<2.102.0-3
2.102.0-3
Microsoft Azure Linux=3.0
All of the following
azurelinux/kube-vip-cloud-provider<0.0.10-12
0.0.10-12
Microsoft Azure Linux=3.0
All of the following
azurelinux/telegraf<1.31.0-37
1.31.0-37
Microsoft Azure Linux=3.0
All of the following
azurelinux/application-gateway-kubernetes-ingress<1.7.7-8
1.7.7-8
Microsoft Azure Linux=3.0
All of the following
azurelinux/cloud-provider-kubevirt<0.5.1-11
0.5.1-11
Microsoft Azure Linux=3.0
All of the following
azurelinux/sriov-network-device-plugin<3.7.0-10
3.7.0-10
Microsoft Azure Linux=3.0
All of the following
azurelinux/kubevirt<1.8.4-5
1.8.4-5
Microsoft Azure Linux=3.0
All of the following
azurelinux/docker-buildx<0.14.0-20
0.14.0-20
Microsoft Azure Linux=3.0
All of the following
azurelinux/docker-compose<2.27.0-17
2.27.0-17
Microsoft Azure Linux=3.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/golang-golang-x-net to a version that resolves this vulnerability.

    Fixed in 1:0.62.0-1
  2. Upgrade

    Upgrade azurelinux/dasel to a version that resolves this vulnerability.

    Fixed in 2.8.1-6
  3. Upgrade

    Upgrade azurelinux/kube-vip-cloud-provider to a version that resolves this vulnerability.

    Fixed in 0.0.10-12
  4. Upgrade

    Upgrade azurelinux/cri-tools to a version that resolves this vulnerability.

    Fixed in 1.32.0-11
  5. Upgrade

    Upgrade azurelinux/gh to a version that resolves this vulnerability.

    Fixed in 2.102.0-3
  6. Upgrade

    Upgrade azurelinux/telegraf to a version that resolves this vulnerability.

    Fixed in 1.31.0-37
  7. Upgrade

    Upgrade azurelinux/application-gateway-kubernetes-ingress to a version that resolves this vulnerability.

    Fixed in 1.7.7-8
  8. Upgrade

    Upgrade azurelinux/cloud-provider-kubevirt to a version that resolves this vulnerability.

    Fixed in 0.5.1-11
  9. Upgrade

    Upgrade azurelinux/sriov-network-device-plugin to a version that resolves this vulnerability.

    Fixed in 3.7.0-10
  10. Upgrade

    Upgrade azurelinux/kubevirt to a version that resolves this vulnerability.

    Fixed in 1.8.4-5
  11. Upgrade

    Upgrade azurelinux/docker-buildx to a version that resolves this vulnerability.

    Fixed in 0.14.0-20
  12. Upgrade

    Upgrade azurelinux/docker-compose to a version that resolves this vulnerability.

    Fixed in 2.27.0-17
  13. Upgrade

    Upgrade azurelinux/telegraf to a version that resolves this vulnerability.

    Fixed in 1.31.0-38

Event History

Oct 27, 2026
CVE Published
via MITRE·09:38 PM
Data Sourced
via MITRE·09:38 PM
DescriptionWeakness
Data Sourced
via OSV·10:18 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·10:18 PM
DescriptionSeverityWeakness
Oct 31, 2026
Data Sourced
via Microsoft·08:07 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:07 AM
Affected Software

Frequently Asked Questions

1

What kind of inputs can trigger the excessive resource use?

Inputs with many short text runs separated by ignored end tags, such as repeated patterns resembling "a</x>", can trigger quadratic allocations and byte copying during HTML parsing.

2

What impact should operators expect from exploitation?

The issue causes excessive CPU and memory work while parsing crafted HTML because the accumulated text was repeatedly reallocated and copied. The provided data does not describe impacts beyond this parsing-time resource consumption.

3

Is an application exposed only if it parses attacker-controlled HTML?

The described trigger requires crafted HTML to be parsed. Applications that do not parse untrusted or externally supplied HTML would not have an attacker-controlled path to supply the triggering input based on the available information.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203