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

35 affected componentsFixes available
go Go net/http
Microsoft azl3 multus 4.0.2-11<4.0.2-12
4.0.2-12
Microsoft azl3 telegraf 1.31.0-33<1.31.0-35
1.31.0-35
Microsoft azl3 cri-tools 1.32.0-8<1.32.0-10
1.32.0-10
Microsoft azl3 cf-cli 8.7.11-9<8.7.11-10
8.7.11-10
Microsoft azl3 skopeo 1.14.4-13<1.14.4-14
1.14.4-14
Microsoft azl3 flannel 0.24.2-32<0.24.2-34
0.24.2-34
Microsoft azl3 docker-cli 25.0.7-5<25.0.7-6
25.0.7-6
Microsoft azl3 docker-compose 2.27.0-14<2.27.0-16
2.27.0-16
Microsoft azl3 containerized-data-importer 1.62.0-8<1.62.0-9
1.62.0-9
Microsoft azl3 docker-buildx 0.14.0-17<0.14.0-19
0.14.0-19
Microsoft azl3 cert-manager 1.12.15-14<1.12.15-15
1.12.15-15
Microsoft azl3 azurelinux-image-tools 1.6.0-3<1.7.0-2
1.7.0-2
Microsoft azl3 cloud-provider-kubevirt 0.5.1-9<0.5.1-10
0.5.1-10
Microsoft azl3 kube-vip-cloud-provider 0.0.10-10<0.0.10-11
0.0.10-11
Microsoft azl3 keda 2.14.1-19<2.14.1-22
2.14.1-22
Microsoft azl3 prometheus-adapter 0.12.0-10<0.12.0-12
0.12.0-12
Microsoft azl3 containerd2 2.3.4-1<2.3.7-1
2.3.7-1
Microsoft azl3 packer 1.9.5-21<1.9.5-23
1.9.5-23
Microsoft azl3 kubevirt 1.8.4-2<1.8.4-4
1.8.4-4
Microsoft azl3 influxdb 2.7.5-21<2.7.5-22
2.7.5-22
Microsoft azl3 coredns 1.11.4-21<1.11.4-23
1.11.4-23
Microsoft azl3 application-gateway-kubernetes-ingress 1.7.7-6<1.7.7-7
1.7.7-7
Microsoft azl3 ignition-flatcar 2.22.0-6<2.22.0-7
2.22.0-7
Microsoft azl3 etcd 3.5.33-1<3.5.35-1
3.5.35-1
Microsoft azl3 opa 0.63.0-5<0.63.0-6
0.63.0-6
Microsoft azl3 prometheus-process-exporter 0.8.2-5<0.8.2-6
0.8.2-6
Microsoft azl3 prometheus-node-exporter 1.7.0-5<1.7.0-6
1.7.0-6
Microsoft azl3 sriov-network-device-plugin 3.7.0-8<3.7.0-9
3.7.0-9
Microsoft azl3 vitess 19.0.4-14<19.0.4-15
19.0.4-15
Microsoft azl3 kured 1.15.0-6<1.15.0-7
1.15.0-7
Microsoft azl3 gh 2.101.0-1<2.102.0-2
2.102.0-2
Microsoft azl3 jx 3.10.182-5<3.10.182-6
3.10.182-6
Microsoft azl3 azcopy 10.25.1-9<10.25.1-10
10.25.1-10
Microsoft azl3 git-lfs 3.6.1-6<3.6.1-7
3.6.1-7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 4.0.2-12
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.31.0-35
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.32.0-10
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.7.11-10
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.14.4-14
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.24.2-34
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 25.0.7-6
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.27.0-16
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.62.0-9
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.14.0-19
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.12.15-15
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.7.0-2
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.5.1-10
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.0.10-11
  15. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.14.1-22
  16. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.12.0-12
  17. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.3.7-1
  18. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.8.4-4
  19. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.9.5-23
  20. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.7.5-22
  21. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.11.4-23
  22. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.7.7-7
  23. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.22.0-7
  24. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.5.35-1
  25. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.63.0-6
  26. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 0.8.2-6
  27. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.7.0-9
  28. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 19.0.4-15
  29. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.15.0-7
  30. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.7.0-6
  31. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.10.182-6
  32. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.25.1-10
  33. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 2.102.0-2
  34. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.6.1-7

Event History

Oct 8, 2026
CVE Published
via MITRE·10:53 PM
Data Sourced
via MITRE·10:53 PM
DescriptionWeakness
Data Sourced
via NVD·11:17 PM
DescriptionSeverityWeakness
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.

Company

Resources

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