Search threats, CVEs… ⌘K
Back to vendor advisories
Microsoft Security Response CenterCVE-2025-53605

The protobuf crate before 3.7.2 for Rust allows uncontrolled recursion in the protobuf::coded_input_stream::CodedInputStream::skip_group parsing of unknown fields in untrusted input.

MediumVendor CVSS 5.9 / 10 1 CVE Published Sep 4, 2025 at 3:26 AM UTC
Get alerts for azl3 kata-containers 3.18.0.kata0-3 on Azure Linux

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 kata-containers 3.18.0.kata0-3 on Azure Linux 3.0

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

  • azl3 rust 1.86.0-4 on Azure Linux 3.0

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

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

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

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

  • cbl2 rust 1.72.0-10 on CBL Mariner 2.0

Show 6 more products

  • cbl2 rust 1.72.0-11 on CBL Mariner 2.0

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

  • azl3 rust 1.75.0-17 on Azure Linux 3.0

  • cbl2 kata-containers 3.2.0.azl2-7 on CBL Mariner 2.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

Remediation

CBL-Mariner Releases Release Notes

Vendor-listed fixes

  • 3.19.1.kata2-1

  • 1.86.0-4

  • 1.72.0-11

  • 1.75.0-17

CVEs in this advisory 1

CVE-2025-53605
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.

Keep investigating
See every advisory from this vendor