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

Tracing logging user input may result in poisoning logs with ANSI escape sequences

Low 1 CVE Published Dec 31, 2025 at 1:02 AM UTC

Summary

Mariner

Products covered

  • azl3 kata-containers 3.19.1.kata2-2 on Azure Linux 3.0

  • azl3 rpm-ostree 2024.4-5 on Azure Linux 3.0

  • azl3 rust 1.75.0-22 on Azure Linux 3.0

  • azl3 rust 1.86.0-10 on Azure Linux 3.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

  • azl3 kata-containers 3.19.1.kata2-3 on Azure Linux 3.0

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

Show 22 more products
  • azl3 rust 1.90.0-1 on Azure Linux 3.0

  • azl3 kata-containers 3.19.1.kata2-4 on Azure Linux 3.0

  • azl3 rust 1.75.0-24 on Azure Linux 3.0

  • azl3 rust 1.90.0-3 on Azure Linux 3.0

  • cbl2 rpm-ostree 2022.1-8 on CBL Mariner 2.0

  • cbl2 rust 1.72.0-13 on CBL Mariner 2.0

  • cbl2 rust 1.72.0-14 on CBL Mariner 2.0

  • azl3 trident 0.21.0-1 on Azure Linux 3.0

  • azl3 kata-containers 3.19.1.kata2-6 on Azure Linux 3.0

  • azl3 rpm-ostree 2024.4-6 on Azure Linux 3.0

  • azl3 rust 1.90.0-4 on Azure Linux 3.0

  • azl3 kata-containers 3.19.1.kata2-7 on Azure Linux 3.0

  • azl3 rpm-ostree 2024.4-8 on Azure Linux 3.0

  • azl3 kata-containers 3.19.1.kata3-1 on Azure Linux 3.0

  • azl3 kata-containers 3.19.1.kata3-5 on Azure Linux 3.0

  • azl3 kata-containers 3.19.1.kata3-6 on Azure Linux 3.0

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

  • cbl2 rpm-ostree 2022.1-7 on CBL Mariner 2.0

  • cbl2 rust 1.72.0-11 on CBL Mariner 2.0

  • azl3 rust 1.75.0-25 on Azure Linux 3.0

  • cbl2 rust 1.72.0-15 on CBL Mariner 2.0

  • azl3 kata-containers 3.19.1.kata3-4 on Azure Linux 3.0

Remediation

CBL-Mariner Releases

Vendor-listed fixes

  • 1.75.0-25

  • 1.90.0-4

  • 2022.1-8

  • 1.72.0-15

  • 0.22.0-1

  • 2024.4-8

  • 3.19.1.kata3-6

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.

  4. Confirmed at the source

    Our collector saw this advisory during a later source check.