Back to vendor advisories
Microsoft Security Response CenterCVE-2025-22872

Incorrect Neutralization of Input During Web Page Generation in x/net in golang.org/x/net

MediumVendor CVSS 6.5 / 10 1 CVE Published Apr 29, 2025 at 12:00 AM UTC

Summary

Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?

One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the most recent and most secure versions of the open source libraries with which the distro is composed. Microsoft is committed to transparency in this work which is why we began publishing CSAF/VEX in October 2025. See this blog post for more information.

If impact to additional products is identified, we will update the CVE to reflect this.

Products covered

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

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

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

  • azl3 containerd2 2.0.0-12 on Azure Linux 3.0

  • cbl2 cni-plugins 1.3.0-8 on CBL Mariner 2.0

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

  • cbl2 helm 3.14.2-6 on CBL Mariner 2.0

  • cbl2 multus 4.0.2-8 on CBL Mariner 2.0

Show 41 more products
  • cbl2 telegraf 1.29.4-16 on CBL Mariner 2.0

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

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

  • azl3 nvidia-container-toolkit 1.17.8-2 on Azure Linux 3.0

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

  • cbl2 cni-plugins 1.3.0-8 on CBL-Mariner 2.0

  • cbl2 kubernetes 1.28.4-18 on CBL-Mariner 2.0

  • cbl2 telegraf 1.29.4-16 on CBL-Mariner 2.0

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

  • cbl2 packer 1.9.5-13 on CBL-Mariner 2.0

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

  • azl3 helm 3.15.2-3 on Azure Linux 3.0

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

  • azl3 packer 1.9.5-9 on Azure Linux 3.0

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

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

  • azl3 gh 2.62.0-8 on Azure Linux 3.0

  • azl3 kubevirt 1.2.0-17 on Azure Linux 3.0

  • azl3 kubernetes 1.30.10-7 on Azure Linux 3.0

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

  • azl3 ig 0.37.0-4 on Azure Linux 3.0

  • azl3 telegraf 1.31.0-10 on Azure Linux 3.0

  • azl3 influxdb 2.7.5-5 on Azure Linux 3.0

  • azl3 multus 4.0.2-5 on Azure Linux 3.0

  • azl3 containerized-data-importer 1.57.0-14 on Azure Linux 3.0

  • azl3 keda 2.14.1-7 on Azure Linux 3.0

  • azl3 cni-plugins 1.4.0-3 on Azure Linux 3.0

  • cbl2 kubernetes 1.28.4-18 on CBL Mariner 2.0

  • cbl2 kubevirt 0.59.0-28 on CBL Mariner 2.0

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

  • cbl2 vitess 17.0.7-8 on CBL Mariner 2.0

  • cbl2 packer 1.9.5-13 on CBL Mariner 2.0

  • azl3 dasel 2.8.1-2 on Azure Linux 3.0

  • cbl2 nvidia-container-toolkit 1.17.8-1 on CBL Mariner 2.0

  • azl3 nvidia-container-toolkit 1.17.8-1 on Azure Linux 3.0

  • cbl2 nvidia-container-toolkit 1.17.8-3 on CBL Mariner 2.0

  • cbl2 helm 3.14.2-6 on CBL-Mariner 2.0

  • cbl2 multus 4.0.2-8 on CBL-Mariner 2.0

  • cbl2 kubevirt 0.59.0-28 on CBL-Mariner 2.0

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

  • cbl2 vitess 17.0.7-8 on CBL-Mariner 2.0

Remediation

CBL-Mariner Releases

Vendor-listed fixes

  • 1.32.0-2

  • 0.14.0-6

  • 1.11.2-23

  • 2.0.0-9

  • 1.3.0-8

  • 1.12.15-4

  • 3.14.2-6

  • 4.0.2-8

Show 28 more fixes
  • 1.29.4-16

  • 3.6.2-9

  • 1.29.0-8

  • 1.17.8-2

  • 1.28.4-18

  • 1.9.5-13

  • 0.0.10-4

  • 3.15.2-3

  • 2.27.0-5

  • 1.9.5-9

  • 0.12.0-3

  • 8.7.11-3

  • 2.62.0-8

  • 1.2.0-17

  • 1.30.10-7

  • 3.7.0-4

  • 0.37.0-4

  • 1.31.0-10

  • 2.7.5-5

  • 4.0.2-5

  • 1.57.0-14

  • 2.14.1-7

  • 1.4.0-3

  • 0.59.0-28

  • 1.29.0-7

  • 17.0.7-8

  • 2.8.1-2

  • 1.17.8-3

CVEs in this advisory 1

Updates

  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.