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

Infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE in net/http/internal/http2 in golang.org/x/net

Mariner

7.5CVSS out of 10Medium severity
Scope

What the vendor says is affected

  • azl3 golang 1.25.9-1 on Azure Linux 3.0
  • azl3 golang 1.26.2-1 on Azure Linux 3.0
  • azl3 application-gateway-kubernetes-ingress 1.7.7-3 on Azure Linux 3.0
  • azl3 azurelinux-image-tools 1.2.0-2 on Azure Linux 3.0
  • azl3 containerd2 2.1.6-2 on Azure Linux 3.0
  • azl3 containerized-data-importer 1.62.0-3 on Azure Linux 3.0
  • azl3 etcd 3.5.28-1 on Azure Linux 3.0
  • azl3 ignition-flatcar 2.22.0-2 on Azure Linux 3.0
  • azl3 kata-containers 3.19.1.kata3-1 on Azure Linux 3.0
  • azl3 kata-containers-cc 3.15.0.aks0-9 on Azure Linux 3.0
  • azl3 kubevirt 1.7.1-2 on Azure Linux 3.0
  • azl3 packer 1.9.5-13 on Azure Linux 3.0
  • azl3 golang 1.24.13-1 on Azure Linux 3.0
  • azl3 azurelinux-image-tools 1.4.0-2 on Azure Linux 3.0
  • azl3 kata-containers 3.19.1.kata3-4 on Azure Linux 3.0
  • azl3 packer 1.9.5-15 on Azure Linux 3.0
  • azl3 cert-manager 1.12.15-6 on Azure Linux 3.0
  • azl3 application-gateway-kubernetes-ingress 1.7.7-5 on Azure Linux 3.0
  • azl3 cert-manager 1.12.15-9 on Azure Linux 3.0
  • azl3 containerd2 2.2.4-2 on Azure Linux 3.0
  • azl3 containerized-data-importer 1.62.0-6 on Azure Linux 3.0
  • azl3 etcd 3.5.30-2 on Azure Linux 3.0
  • azl3 ignition-flatcar 2.22.0-5 on Azure Linux 3.0
  • azl3 kata-containers-cc 3.15.0.aks0-12 on Azure Linux 3.0

Versions the vendor lists as fixed

  • 1.26.3-1
  • 1.7.7-4
  • 1.3.0-2
  • 2.1.6-4
  • 1.62.0-4
  • 3.5.30-2
  • 2.22.0-4
  • 3.19.1.kata3-3
  • 3.15.0.aks0-11
  • 1.7.1-4
  • 1.9.5-14
  • 1.4.0-2
  • 3.19.1.kata3-4
  • 1.9.5-15
  • 1.12.15-7
  • 1.7.7-5
  • 1.12.15-9
  • 2.2.4-2
  • 1.62.0-6
  • 2.22.0-5
  • 3.15.0.aks0-12
  • 1.7.1-7
Next step

What the vendor recommends

CBL-Mariner Releases

Review the complete instructions on the vendor's site
Timeline

When this advisory changed

  1. Published by Microsoft Security Response Center

    The publication date reported by the vendor.

  2. Updated by Microsoft Security Response Center

    The vendor changed the advisory after it was first published.

  3. Added to SecurityAlert

    We collected the advisory from the official source.

Vulnerabilities

CVEs named in this advisory