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

OpenTelemetry-Go multi-value `baggage` header extraction causes excessive allocations (remote dos amplification)

MediumVendor CVSS 7.5 / 10 1 CVE Published Apr 11, 2026 at 1:03 AM UTC

Summary

Mariner

Products covered

  • azl3 containerd2 2.1.6-1 on Azure Linux 3.0

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

  • azl3 gh 2.62.0-15 on Azure Linux 3.0

  • azl3 telegraf 1.31.0-19 on Azure Linux 3.0

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

  • cbl2 etcd 3.5.28-1

  • cbl2 etcd 3.5.28-1 on CBL-Mariner 2.0

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

Show 13 more products
  • azl3 cloud-provider-kubevirt 0.5.1-3 on Azure Linux 3.0

  • azl3 containerd2 2.0.0-18 on Azure Linux 3.0

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

  • azl3 coredns 1.11.4-15 on Azure Linux 3.0

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

  • cbl2 etcd 3.5.28-1 on CBL Mariner 2.0

  • azl3 etcd 3.5.28-1 on Azure Linux 3.0

  • azl3 gh 2.62.0-13 on Azure Linux 3.0

  • azl3 keda 2.14.1-11 on Azure Linux 3.0

  • azl3 telegraf 1.31.0-17 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

  • azl3 etcd 3.5.30-2 on Azure Linux 3.0

Remediation

CBL-Mariner Releases Release Notes

Vendor-listed fixes

  • 2.22.0-5

  • 1.3.0-1

  • 3.5.30-2

  • 2.22.0-3

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.

    • Added affected products: azl3 etcd 3.5.30-2 on Azure Linux 3.0, azl3 ignition-flatcar 2.22.0-2 on Azure Linux 3.0, azl3 ignition-flatcar 2.22.0-5 on Azure Linux 3.0, cbl2 etcd 3.5.28-1, cbl2 etcd 3.5.28-1 on CBL-Mariner 2.0.
    • Added fixed versions: 1.3.0-1, 2.22.0-3, 2.22.0-5, 3.5.30-2.
    • The vendor changed its remediation guidance.

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.

  4. Confirmed at the source

    Our collector saw this advisory during a later source check.