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

github.com/moby/sys/user has a possible DoS via unbounded parsing of user and group database files

MediumVendor CVSS 5.5 / 10 1 CVE Published Oct 11, 2026 at 1:50 AM UTC

Summary

Mariner

Products covered

  • azl3 containerd2 2.3.4-1 on Azure Linux 3.0

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

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

  • azl3 kata-containers 4.1.0.kata0-1 on Azure Linux 3.0

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

  • azl3 kubernetes 1.30.10-30 on Azure Linux 3.0

  • azl3 kubevirt 1.8.4-2 on Azure Linux 3.0

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

Show 3 more products
  • azl3 httpd 2.4.68-1 on Azure Linux 3.0

  • azl3 skopeo 1.14.4-13 on Azure Linux 3.0

  • azl3 telegraf 1.31.0-33 on Azure Linux 3.0

Remediation

Release Notes

Vendor-listed fixes

  • 2.3.7-1

  • 1.62.0-9

  • 2.27.0-16

  • 1.8.4-4

  • 25.0.18-1

  • 1.4.3-2

  • 1.14.4-14

  • 1.31.0-35

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 fixed versions: 1.8.4-4, 2.3.7-1.
    • Added fixed versions: 1.4.3-2, 1.62.0-9, 2.27.0-16, 25.0.18-1.
    • Removed affected products: azl3 docker-buildx 0.14.0-17 on Azure Linux 3.0, azl3 docker-cli 25.0.7-5 on Azure Linux 3.0, azl3 libcontainers-common 20240213-3 on Azure Linux 3.0.
    • Added fixed versions: 1.14.4-14, 1.31.0-35.
    • Added affected products: azl3 containerd2 2.3.4-1 on Azure Linux 3.0, azl3 containerized-data-importer 1.62.0-8 on Azure Linux 3.0, azl3 docker-buildx 0.14.0-17 on Azure Linux 3.0, azl3 docker-cli 25.0.7-5 on Azure Linux 3.0, azl3 docker-compose....

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.