CVE-2026-78659

High

Description

When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently.

SeverityHigh
CVSS7.5
Exploit probability—
ProductStdlib
PublishedOct 8, 2026
First seenOct 8, 2026
Weakness typeCWE-405CWE-405

How to fix

Update
  • stdlib1.26.9, 1.27.2 or later
  • golang.org/x/net0.60.0 or later

Affected products

ProductAffected versionsFixed in
stdlibGov < 1.26.9, 1.27.0-0 ≤ v < 1.27.21.26.9, 1.27.2
golang.org/x/netGov < 0.60.00.60.0
microsoft azl3_application-gateway-kubernetes-ingress_1.7.7-6No range specified—
microsoft azl3_azurelinux-image-tools_1.6.0-3No range specified—
microsoft azl3_cert-manager_1.12.15-14No range specified—
microsoft azl3_cloud-provider-kubevirt_0.5.1-9No range specified—
microsoft azl3_containerd2_2.3.4-1No range specified—
microsoft azl3_containerized-data-importer_1.62.0-8No range specified—
microsoft azl3_coredns_1.11.4-21No range specified—
microsoft azl3_docker-buildx_0.14.0-17No range specified—
microsoft azl3_docker-compose_2.27.0-14No range specified—
microsoft azl3_etcd_3.5.33-1No range specified—
microsoft azl3_flannel_0.24.2-32No range specified—
microsoft azl3_gh_2.101.0-1No range specified—
microsoft azl3_git-lfs_3.6.1-6No range specified—
microsoft azl3_influxdb_2.7.5-21No range specified—
microsoft azl3_jx_3.10.182-5No range specified—
microsoft azl3_kata-containers_4.1.0.kata0-1No range specified—
microsoft azl3_kata-containers-cc_3.15.0.aks0-21No range specified—
microsoft azl3_keda_2.14.1-19No range specified—
microsoft azl3_kube-vip-cloud-provider_0.0.10-10No range specified—
microsoft azl3_kubernetes_1.30.10-30No range specified—
microsoft azl3_kubevirt_1.8.4-2No range specified—
microsoft azl3_kured_1.15.0-6No range specified—
microsoft azl3_moby-containerd-cc_1.7.7-17No range specified—
microsoft azl3_moby-engine_25.0.3-20No range specified—
microsoft azl3_multus_4.0.2-11No range specified—
microsoft azl3_opa_0.63.0-5No range specified—
microsoft azl3_packer_1.9.5-21No range specified—
microsoft azl3_prometheus-adapter_0.12.0-10No range specified—
microsoft azl3_prometheus-node-exporter_1.7.0-5No range specified—
microsoft azl3_prometheus-process-exporter_0.8.2-5No range specified—
microsoft azl3_skopeo_1.14.4-13No range specified—
microsoft azl3_telegraf_1.31.0-33No range specified—
microsoft azl3_vitess_19.0.4-14No range specified—
microsoft azl3_golang_1.26.7-1No range specified—
microsoft azl3_golang_1.27.1-1No range specified—
microsoft azl3_kata-containers_4.1.0.kata1-2No range specified—
microsoft azl3_kata-containers-cc_3.15.0.aks0-23No range specified—
microsoft azl3_kubernetes_1.30.10-32No range specified—
microsoft azl3_moby-containerd-cc_1.7.7-19No range specified—
microsoft azl3_moby-engine_25.0.18-1No range specified—
microsoft azl3_golang_1.26.10-1No range specified—
microsoft azl3_golang_1.27.3-1No range specified—
microsoft azl3_kubevirt-openvmm_1.9.0-1No range specified—

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.