CVE-2026-97032: HTTP/2 server crash due to HPACK encoder race in net/http

Published Oct 8, 2026
·
Updated

HTTP/2 server crash due to HPACK encoder race in net/http

Other sources

HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGSHEADERTABLESIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.

— MITRE

Affected Software

67 affected componentsFixes available
go/net/http
All of the following
azurelinux/etcd<3.5.35-1
3.5.35-1
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/gh<2.102.0-2
2.102.0-2
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/influxdb<2.7.5-22
2.7.5-22
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/vitess<19.0.4-15
19.0.4-15
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/coredns<1.11.4-23
1.11.4-23
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/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/docker-buildx<0.14.0-19
0.14.0-19
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/prometheus-node-exporter<1.7.0-6
1.7.0-6
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/containerized-data-importer<1.62.0-9
1.62.0-9
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/prometheus-process-exporter<0.8.2-6
0.8.2-6
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/docker-compose<2.27.0-16
2.27.0-16
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/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/skopeo<1.14.4-14
1.14.4-14
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/cloud-provider-kubevirt<0.5.1-10
0.5.1-10
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/kata-containers<4.1.0.kata1-2
4.1.0.kata1-2
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-cc<3.15.0.aks0-23
3.15.0.aks0-23
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
alpine/docker<29.9.0-r0
29.9.0-r0
alpine/go<1.26.9-r0
1.26.9-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 3.5.35-1
  2. Upgrade

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

    Fixed in 1.7.7-7
  3. Upgrade

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

    Fixed in 2.102.0-2
  4. Upgrade

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

    Fixed in 0.63.0-6
  5. Upgrade

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

    Fixed in 2.7.5-22
  6. Upgrade

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

    Fixed in 3.10.182-6
  7. Upgrade

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

    Fixed in 19.0.4-15
  8. Upgrade

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

    Fixed in 3.6.1-7
  9. Upgrade

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

    Fixed in 1.11.4-23
  10. Upgrade

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

    Fixed in 0.12.0-12
  11. Upgrade

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

    Fixed in 1.9.5-23
  12. Upgrade

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

    Fixed in 1.8.4-4
  13. Upgrade

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

    Fixed in 0.14.0-19
  14. Upgrade

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

    Fixed in 2.3.7-1
  15. Upgrade

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

    Fixed in 0.0.10-11
  16. Upgrade

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

    Fixed in 1.7.0-6
  17. Upgrade

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

    Fixed in 1.62.0-9
  18. Upgrade

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

    Fixed in 0.8.2-6
  19. Upgrade

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

    Fixed in 0.24.2-34
  20. Upgrade

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

    Fixed in 2.14.1-22
  21. Upgrade

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

    Fixed in 2.27.0-16
  22. Upgrade

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

    Fixed in 1.15.0-7
  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/skopeo to a version that resolves this vulnerability.

    Fixed in 1.14.4-14
  26. Upgrade

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

    Fixed in 4.0.2-12
  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/kata-containers to a version that resolves this vulnerability.

    Fixed in 4.1.0.kata1-2
  30. Upgrade

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

    Fixed in 1.30.10-32
  31. Upgrade

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

    Fixed in 3.15.0.aks0-23
  32. Upgrade

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

    Fixed in 1.7.7-19
  33. Upgrade

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

    Fixed in 29.9.0-r0
  34. Upgrade

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

    Fixed in 1.26.9-r0

Event History

Oct 8, 2026
CVE Published
via MITRE·10:54 PM
Data Sourced
via MITRE·10:54 PM
DescriptionWeakness
Data Sourced
via NVD·11:17 PM
DescriptionSeverityWeakness
Data Sourced
via OSV·11:17 PM
DescriptionSeverityAffected Software
Oct 11, 2026
Data Sourced
via Microsoft·08:40 AM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What does an attacker need to do to trigger the crash?

The attacker needs to interact with an HTTP/2 server and repeatedly send requests while sending SETTINGS frames that change SETTINGS_HEADER_TABLE_SIZE. The race occurs between response HEADERS encoding and processing the client-controlled header-table-size setting.

2

Which deployments are exposed?

Deployments using Go's net/http package as an HTTP/2 server are exposed to the described crash condition. The provided information does not identify any configuration prerequisite beyond serving HTTP/2.

3

What is the likely impact of successful exploitation?

Successful exploitation can crash the HTTP/2 server, resulting in denial of service. The provided information describes a concurrency race in the HPACK encoder and does not state any impact beyond server crashes.

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