CVE-2026-78669: Excessive CPU consumption from repeated initial window changes in net/http

Published Oct 8, 2026
·
Updated

A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGSINITIALWINDOWSIZE values.

Other sources

Excessive CPU consumption from repeated initial window changes in net/http

— Microsoft

Affected Software

82 affected componentsFixes available
go Go net/http
All of the following
azurelinux/prometheus-process-exporter<0.8.2-6
0.8.2-6
Microsoft Azure Linux=3.0
All of the following
azurelinux/gh<2.102.0-2
2.102.0-2
Microsoft Azure Linux=3.0
All of the following
azurelinux/prometheus-node-exporter<1.7.0-6
1.7.0-6
Microsoft Azure Linux=3.0
All of the following
azurelinux/jx<3.10.182-6
3.10.182-6
Microsoft Azure Linux=3.0
All of the following
azurelinux/sriov-network-device-plugin<3.7.0-9
3.7.0-9
Microsoft Azure Linux=3.0
All of the following
azurelinux/vitess<19.0.4-15
19.0.4-15
Microsoft Azure Linux=3.0
All of the following
azurelinux/kured<1.15.0-7
1.15.0-7
Microsoft Azure Linux=3.0
All of the following
azurelinux/opa<0.63.0-6
0.63.0-6
Microsoft Azure Linux=3.0
All of the following
azurelinux/application-gateway-kubernetes-ingress<1.7.7-7
1.7.7-7
Microsoft Azure Linux=3.0
All of the following
azurelinux/git-lfs<3.6.1-7
3.6.1-7
Microsoft Azure Linux=3.0
All of the following
azurelinux/ignition-flatcar<2.22.0-7
2.22.0-7
Microsoft Azure Linux=3.0
All of the following
azurelinux/prometheus-adapter<0.12.0-12
0.12.0-12
Microsoft Azure Linux=3.0
All of the following
azurelinux/influxdb<2.7.5-22
2.7.5-22
Microsoft Azure Linux=3.0
All of the following
azurelinux/etcd<3.5.35-1
3.5.35-1
Microsoft Azure Linux=3.0
All of the following
azurelinux/packer<1.9.5-23
1.9.5-23
Microsoft Azure Linux=3.0
All of the following
azurelinux/kubevirt<1.8.4-4
1.8.4-4
Microsoft Azure Linux=3.0
All of the following
azurelinux/containerd2<2.3.7-1
2.3.7-1
Microsoft Azure Linux=3.0
All of the following
azurelinux/keda<2.14.1-22
2.14.1-22
Microsoft Azure Linux=3.0
All of the following
azurelinux/coredns<1.11.4-23
1.11.4-23
Microsoft Azure Linux=3.0
All of the following
azurelinux/azcopy<10.25.1-10
10.25.1-10
Microsoft Azure Linux=3.0
All of the following
azurelinux/kube-vip-cloud-provider<0.0.10-11
0.0.10-11
Microsoft Azure Linux=3.0
All of the following
azurelinux/docker-buildx<0.14.0-19
0.14.0-19
Microsoft Azure Linux=3.0
All of the following
azurelinux/cert-manager<1.12.15-15
1.12.15-15
Microsoft Azure Linux=3.0
All of the following
azurelinux/azurelinux-image-tools<1.7.0-2
1.7.0-2
Microsoft Azure Linux=3.0
All of the following
azurelinux/docker-compose<2.27.0-16
2.27.0-16
Microsoft Azure Linux=3.0
All of the following
azurelinux/flannel<0.24.2-34
0.24.2-34
Microsoft Azure Linux=3.0
All of the following
azurelinux/telegraf<1.31.0-35
1.31.0-35
Microsoft Azure Linux=3.0
All of the following
azurelinux/cloud-provider-kubevirt<0.5.1-10
0.5.1-10
Microsoft Azure Linux=3.0
All of the following
azurelinux/docker-cli<25.0.7-6
25.0.7-6
Microsoft Azure Linux=3.0
All of the following
azurelinux/containerized-data-importer<1.62.0-9
1.62.0-9
Microsoft Azure Linux=3.0
All of the following
azurelinux/skopeo<1.14.4-14
1.14.4-14
Microsoft Azure Linux=3.0
All of the following
azurelinux/cf-cli<8.7.11-10
8.7.11-10
Microsoft Azure Linux=3.0
All of the following
azurelinux/cri-tools<1.32.0-10
1.32.0-10
Microsoft Azure Linux=3.0
All of the following
azurelinux/multus<4.0.2-12
4.0.2-12
Microsoft Azure Linux=3.0
All of the following
azurelinux/kubernetes<1.30.10-32
1.30.10-32
Microsoft Azure Linux=3.0
All of the following
azurelinux/kata-containers<4.1.0.kata1-2
4.1.0.kata1-2
Microsoft Azure Linux=3.0
All of the following
azurelinux/moby-containerd-cc<1.7.7-19
1.7.7-19
Microsoft Azure Linux=3.0
All of the following
azurelinux/kata-containers-cc<3.15.0.aks0-23
3.15.0.aks0-23
Microsoft Azure Linux=3.0
alpine/docker<29.9.0-r0
29.9.0-r0
alpine/go<1.26.9-r0
1.26.9-r0
go/stdlib<1.26.9
1.26.9
go/stdlib>=1.27.0-0<1.27.2
1.27.2
go/golang.org/x/net<0.60.0
0.60.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade azurelinux/prometheus-process-exporter to a version that resolves this vulnerability.

    Fixed in 0.8.2-6
  2. Upgrade

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

    Fixed in 2.102.0-2
  3. Upgrade

    Upgrade azurelinux/prometheus-node-exporter to a version that resolves this vulnerability.

    Fixed in 1.7.0-6
  4. Upgrade

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

    Fixed in 3.10.182-6
  5. Upgrade

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

    Fixed in 3.7.0-9
  6. Upgrade

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

    Fixed in 19.0.4-15
  7. Upgrade

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

    Fixed in 1.15.0-7
  8. Upgrade

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

    Fixed in 0.63.0-6
  9. Upgrade

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

    Fixed in 1.7.7-7
  10. Upgrade

    Upgrade azurelinux/git-lfs to a version that resolves this vulnerability.

    Fixed in 3.6.1-7
  11. Upgrade

    Upgrade azurelinux/ignition-flatcar to a version that resolves this vulnerability.

    Fixed in 2.22.0-7
  12. Upgrade

    Upgrade azurelinux/prometheus-adapter to a version that resolves this vulnerability.

    Fixed in 0.12.0-12
  13. Upgrade

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

    Fixed in 2.7.5-22
  14. Upgrade

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

    Fixed in 3.5.35-1
  15. Upgrade

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

    Fixed in 1.9.5-23
  16. Upgrade

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

    Fixed in 1.8.4-4
  17. Upgrade

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

    Fixed in 2.3.7-1
  18. Upgrade

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

    Fixed in 2.14.1-22
  19. Upgrade

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

    Fixed in 1.11.4-23
  20. Upgrade

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

    Fixed in 10.25.1-10
  21. Upgrade

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

    Fixed in 0.0.10-11
  22. Upgrade

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

    Fixed in 0.14.0-19
  23. Upgrade

    Upgrade azurelinux/cert-manager to a version that resolves this vulnerability.

    Fixed in 1.12.15-15
  24. Upgrade

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

    Fixed in 1.7.0-2
  25. Upgrade

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

    Fixed in 2.27.0-16
  26. Upgrade

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

    Fixed in 0.24.2-34
  27. Upgrade

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

    Fixed in 1.31.0-35
  28. Upgrade

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

    Fixed in 0.5.1-10
  29. Upgrade

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

    Fixed in 25.0.7-6
  30. Upgrade

    Upgrade azurelinux/containerized-data-importer to a version that resolves this vulnerability.

    Fixed in 1.62.0-9
  31. Upgrade

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

    Fixed in 1.14.4-14
  32. Upgrade

    Upgrade azurelinux/cf-cli to a version that resolves this vulnerability.

    Fixed in 8.7.11-10
  33. Upgrade

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

    Fixed in 1.32.0-10
  34. Upgrade

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

    Fixed in 4.0.2-12
  35. Upgrade

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

    Fixed in 1.30.10-32
  36. Upgrade

    Upgrade azurelinux/kata-containers to a version that resolves this vulnerability.

    Fixed in 4.1.0.kata1-2
  37. Upgrade

    Upgrade azurelinux/moby-containerd-cc to a version that resolves this vulnerability.

    Fixed in 1.7.7-19
  38. Upgrade

    Upgrade azurelinux/kata-containers-cc to a version that resolves this vulnerability.

    Fixed in 3.15.0.aks0-23
  39. Upgrade

    Upgrade alpine/docker to a version that resolves this vulnerability.

    Fixed in 29.9.0-r0
  40. Upgrade

    Upgrade alpine/go to a version that resolves this vulnerability.

    Fixed in 1.26.9-r0
  41. Upgrade

    Upgrade go/stdlib to a version that resolves this vulnerability.

    Fixed in 1.26.9
  42. Upgrade

    Upgrade go/stdlib to a version that resolves this vulnerability.

    Fixed in 1.27.2
  43. Upgrade

    Upgrade go/golang.org/x/net to a version that resolves this vulnerability.

    Fixed in 0.60.0

Event History

Oct 8, 2026
Advisory Published
via OSV·10:31 PM
Data Sourced
via OSV·10:31 PM
DescriptionAffected Software
CVE Published
via MITRE·10:53 PM
Data Sourced
via MITRE·10:53 PM
DescriptionWeakness
Data Sourced
via Red Hat·11:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·11:17 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·11:17 PM
Severity
Oct 11, 2026
Data Sourced
via Microsoft·08:29 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which Go applications are exposed to this issue?

Go applications using net/http as an HTTP/2 client or server can be exposed when communicating with a malicious HTTP/2 peer.

2

What does an attacker need to do to trigger the CPU consumption?

The attacker needs to act as an HTTP/2 peer, open a large number of streams, and send many small SETTINGS frames that contain SETTINGS_INITIAL_WINDOW_SIZE values.

3

What is the practical impact of exploitation?

Exploitation can cause excessive CPU consumption in the affected net/http HTTP/2 client or server.

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