Back to vendor advisories
Microsoft Security Response CenterCVE-2026-27141

Sending certain HTTP/2 frames can cause a server to panic in golang.org/x/net

MediumVendor CVSS 7.5 / 10 1 CVE Published Mar 5, 2026 at 1:08 AM UTC

Summary

Mariner

Products covered

  • cbl2 azcopy 10.25.1-6 on CBL Mariner 2.0

  • azl3 azcopy 10.25.1-4 on Azure Linux 3.0

  • azl3 azurelinux-image-tools 1.2.0-1 on Azure Linux 3.0

  • cbl2 cri-tools 1.29.0-9 on CBL Mariner 2.0

  • azl3 cf-cli 8.7.11-5 on Azure Linux 3.0

  • azl3 containerized-data-importer 1.62.0-2 on Azure Linux 3.0

  • azl3 coredns 1.11.4-14 on Azure Linux 3.0

  • azl3 docker-cli 25.0.7-2 on Azure Linux 3.0

Show 59 more products
  • cbl2 git-lfs 3.5.1-6 on CBL Mariner 2.0

  • azl3 etcd 3.5.21-1 on Azure Linux 3.0

  • azl3 flannel 0.24.2-24 on Azure Linux 3.0

  • cbl2 kata-containers 3.2.0.azl2-7 on CBL Mariner 2.0

  • cbl2 kata-containers-cc 3.2.0.azl2-8 on CBL Mariner 2.0

  • cbl2 kubevirt 0.59.0-38 on CBL Mariner 2.0

  • cbl2 moby-containerd 1.6.26-13 on CBL Mariner 2.0

  • cbl2 moby-containerd-cc 1.7.7-13 on CBL Mariner 2.0

  • cbl2 multus 4.0.2-10 on CBL Mariner 2.0

  • cbl2 node-problem-detector 0.8.17-7 on CBL Mariner 2.0

  • azl3 kata-containers 3.19.1.kata2-6 on Azure Linux 3.0

  • cbl2 opa 0.63.0-6 on CBL Mariner 2.0

  • azl3 kube-vip-cloud-provider 0.0.10-5 on Azure Linux 3.0

  • azl3 kubevirt 1.7.0-3 on Azure Linux 3.0

  • azl3 libcontainers-common 20240213-3 on Azure Linux 3.0

  • azl3 moby-containerd-cc 1.7.7-10 on Azure Linux 3.0

  • azl3 opa 0.63.0-3 on Azure Linux 3.0

  • azl3 prometheus-adapter 0.12.0-5 on Azure Linux 3.0

  • cbl2 skopeo 1.14.2-14 on CBL Mariner 2.0

  • cbl2 vitess 17.0.7-14 on CBL Mariner 2.0

  • azl3 skopeo 1.14.4-8 on Azure Linux 3.0

  • azl3 sriov-network-device-plugin 3.7.0-5 on Azure Linux 3.0

  • azl3 telegraf 1.31.0-15 on Azure Linux 3.0

  • cbl2 cert-manager 1.11.2-27 on CBL Mariner 2.0

  • azl3 application-gateway-kubernetes-ingress 1.7.7-3 on Azure Linux 3.0

  • cbl2 coredns 1.11.1-25 on CBL Mariner 2.0

  • azl3 cert-manager 1.12.15-6 on Azure Linux 3.0

  • azl3 cloud-provider-kubevirt 0.5.1-3 on Azure Linux 3.0

  • cbl2 etcd 3.5.21-4 on CBL Mariner 2.0

  • azl3 containerd2 2.0.0-18 on Azure Linux 3.0

  • azl3 cri-tools 1.32.0-4 on Azure Linux 3.0

  • azl3 docker-buildx 0.14.0-10 on Azure Linux 3.0

  • azl3 docker-compose 2.27.0-8 on Azure Linux 3.0

  • cbl2 helm 3.14.2-10 on CBL Mariner 2.0

  • azl3 gh 2.62.0-13 on Azure Linux 3.0

  • azl3 git-lfs 3.6.1-2 on Azure Linux 3.0

  • cbl2 kubernetes 1.28.4-25 on CBL Mariner 2.0

  • cbl2 kured 1.14.2-7 on CBL Mariner 2.0

  • cbl2 moby-cli 24.0.9-8 on CBL Mariner 2.0

  • cbl2 moby-compose 2.17.3-14 on CBL Mariner 2.0

  • cbl2 moby-engine 24.0.9-19 on CBL Mariner 2.0

  • azl3 influxdb 2.7.5-13 on Azure Linux 3.0

  • azl3 jx 3.10.182-3 on Azure Linux 3.0

  • azl3 kata-containers-cc 3.15.0.aks0-7 on Azure Linux 3.0

  • cbl2 packer 1.9.5-18 on CBL Mariner 2.0

  • azl3 keda 2.14.1-11 on Azure Linux 3.0

  • azl3 kubernetes 1.30.10-21 on Azure Linux 3.0

  • cbl2 prometheus 2.37.9-7 on CBL Mariner 2.0

  • azl3 kured 1.15.0-3 on Azure Linux 3.0

  • azl3 moby-engine 25.0.3-14 on Azure Linux 3.0

  • azl3 multus 4.0.2-7 on Azure Linux 3.0

  • azl3 packer 1.9.5-13 on Azure Linux 3.0

  • azl3 prometheus-node-exporter 1.7.0-3 on Azure Linux 3.0

  • azl3 prometheus-process-exporter 0.8.2-3 on Azure Linux 3.0

  • cbl2 sriov-network-device-plugin 3.6.2-11 on CBL Mariner 2.0

  • cbl2 telegraf 1.29.4-21 on CBL Mariner 2.0

  • azl3 vitess 19.0.4-9 on Azure Linux 3.0

  • azl3 ignition-flatcar 2.22.0-1 on Azure Linux 3.0

  • azl3 ignition-flatcar 2.22.0-2 on Azure Linux 3.0

Remediation

CBL-Mariner Releases

Vendor-listed fixes

  • 1.2.0-2

  • 2.22.0-2

CVEs in this advisory 1

Update history

What changed in later vendor updates

SecurityAlert records field-level changes from the point we begin following a bulletin. Earlier vendor changes may not have a field-by-field record.

    • The vendor changed the advisory's last-updated date.

Updates

  1. Published by Microsoft Security Response Center

    The publication date reported by the vendor.

  2. Added to SecurityAlert

    We collected the advisory from the official source.

  3. Updated by Microsoft Security Response Center

    The vendor changed the advisory after it was first published.

  4. Confirmed at the source

    Our collector saw this advisory during a later source check.