CVE-2026-78669: Excessive CPU consumption from repeated initial window changes in net/http
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
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
azurelinux/prometheus-process-exporterto a version that resolves this vulnerability.Fixed in 0.8.2-6 - Upgrade
Upgrade
azurelinux/ghto a version that resolves this vulnerability.Fixed in 2.102.0-2 - Upgrade
Upgrade
azurelinux/prometheus-node-exporterto a version that resolves this vulnerability.Fixed in 1.7.0-6 - Upgrade
Upgrade
azurelinux/jxto a version that resolves this vulnerability.Fixed in 3.10.182-6 - Upgrade
Upgrade
azurelinux/sriov-network-device-pluginto a version that resolves this vulnerability.Fixed in 3.7.0-9 - Upgrade
Upgrade
azurelinux/vitessto a version that resolves this vulnerability.Fixed in 19.0.4-15 - Upgrade
Upgrade
azurelinux/kuredto a version that resolves this vulnerability.Fixed in 1.15.0-7 - Upgrade
Upgrade
azurelinux/opato a version that resolves this vulnerability.Fixed in 0.63.0-6 - Upgrade
Upgrade
azurelinux/application-gateway-kubernetes-ingressto a version that resolves this vulnerability.Fixed in 1.7.7-7 - Upgrade
Upgrade
azurelinux/git-lfsto a version that resolves this vulnerability.Fixed in 3.6.1-7 - Upgrade
Upgrade
azurelinux/ignition-flatcarto a version that resolves this vulnerability.Fixed in 2.22.0-7 - Upgrade
Upgrade
azurelinux/prometheus-adapterto a version that resolves this vulnerability.Fixed in 0.12.0-12 - Upgrade
Upgrade
azurelinux/influxdbto a version that resolves this vulnerability.Fixed in 2.7.5-22 - Upgrade
Upgrade
azurelinux/etcdto a version that resolves this vulnerability.Fixed in 3.5.35-1 - Upgrade
Upgrade
azurelinux/packerto a version that resolves this vulnerability.Fixed in 1.9.5-23 - Upgrade
Upgrade
azurelinux/kubevirtto a version that resolves this vulnerability.Fixed in 1.8.4-4 - Upgrade
Upgrade
azurelinux/containerd2to a version that resolves this vulnerability.Fixed in 2.3.7-1 - Upgrade
Upgrade
azurelinux/kedato a version that resolves this vulnerability.Fixed in 2.14.1-22 - Upgrade
Upgrade
azurelinux/corednsto a version that resolves this vulnerability.Fixed in 1.11.4-23 - Upgrade
Upgrade
azurelinux/azcopyto a version that resolves this vulnerability.Fixed in 10.25.1-10 - Upgrade
Upgrade
azurelinux/kube-vip-cloud-providerto a version that resolves this vulnerability.Fixed in 0.0.10-11 - Upgrade
Upgrade
azurelinux/docker-buildxto a version that resolves this vulnerability.Fixed in 0.14.0-19 - Upgrade
Upgrade
azurelinux/cert-managerto a version that resolves this vulnerability.Fixed in 1.12.15-15 - Upgrade
Upgrade
azurelinux/azurelinux-image-toolsto a version that resolves this vulnerability.Fixed in 1.7.0-2 - Upgrade
Upgrade
azurelinux/docker-composeto a version that resolves this vulnerability.Fixed in 2.27.0-16 - Upgrade
Upgrade
azurelinux/flannelto a version that resolves this vulnerability.Fixed in 0.24.2-34 - Upgrade
Upgrade
azurelinux/telegrafto a version that resolves this vulnerability.Fixed in 1.31.0-35 - Upgrade
Upgrade
azurelinux/cloud-provider-kubevirtto a version that resolves this vulnerability.Fixed in 0.5.1-10 - Upgrade
Upgrade
azurelinux/docker-clito a version that resolves this vulnerability.Fixed in 25.0.7-6 - Upgrade
Upgrade
azurelinux/containerized-data-importerto a version that resolves this vulnerability.Fixed in 1.62.0-9 - Upgrade
Upgrade
azurelinux/skopeoto a version that resolves this vulnerability.Fixed in 1.14.4-14 - Upgrade
Upgrade
azurelinux/cf-clito a version that resolves this vulnerability.Fixed in 8.7.11-10 - Upgrade
Upgrade
azurelinux/cri-toolsto a version that resolves this vulnerability.Fixed in 1.32.0-10 - Upgrade
Upgrade
azurelinux/multusto a version that resolves this vulnerability.Fixed in 4.0.2-12 - Upgrade
Upgrade
azurelinux/kubernetesto a version that resolves this vulnerability.Fixed in 1.30.10-32 - Upgrade
Upgrade
azurelinux/kata-containersto a version that resolves this vulnerability.Fixed in 4.1.0.kata1-2 - Upgrade
Upgrade
azurelinux/moby-containerd-ccto a version that resolves this vulnerability.Fixed in 1.7.7-19 - Upgrade
Upgrade
azurelinux/kata-containers-ccto a version that resolves this vulnerability.Fixed in 3.15.0.aks0-23 - Upgrade
Upgrade
alpine/dockerto a version that resolves this vulnerability.Fixed in 29.9.0-r0 - Upgrade
Upgrade
alpine/goto a version that resolves this vulnerability.Fixed in 1.26.9-r0 - Upgrade
Upgrade
go/stdlibto a version that resolves this vulnerability.Fixed in 1.26.9 - Upgrade
Upgrade
go/stdlibto a version that resolves this vulnerability.Fixed in 1.27.2 - Upgrade
Upgrade
go/golang.org/x/netto a version that resolves this vulnerability.Fixed in 0.60.0
Event History
Frequently Asked Questions
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.
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.
What is the practical impact of exploitation?
Exploitation can cause excessive CPU consumption in the affected net/http HTTP/2 client or server.