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

tar-rs: unpack_in can chmod arbitrary directories by following symlinks

MediumVendor CVSS 6.5 / 10 1 CVE Published Mar 25, 2026 at 1:01 AM UTC

Summary

Mariner

Products covered

  • azl3 kata-containers-cc 3.15.0.aks0-7 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-cc 3.15.0.aks0-8 on Azure Linux 3.0

  • cbl2 rust 1.72.0-15 on CBL Mariner 2.0

  • azl3 rust 1.75.0-27 on Azure Linux 3.0

  • azl3 rust 1.90.0-6 on Azure Linux 3.0

  • azl3 clamav 1.5.2-1 on Azure Linux 3.0

Show 12 more products
  • azl3 clamav 1.5.2-2 on Azure Linux 3.0

  • cbl2 rust 1.72.0-15 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

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

  • cbl2 rust 1.72.0-14 on CBL Mariner 2.0

  • azl3 rust 1.75.0-25 on Azure Linux 3.0

  • azl3 trident 0.21.0-1 on Azure Linux 3.0

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

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

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

  • azl4 fido-device-onboard 0.5.5-13.azl4 on Azure Linux 4.0

Remediation

CBL-Mariner Releases Release Notes

Vendor-listed fixes

  • 1.72.0-16

  • 1.75.0-28

  • 1.90.0-7

  • 1.5.2-2

  • 2022.1-9

  • 0.22.0-1

  • 2024.4-10

  • 0:0.5.5-13.azl4

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.

    • CVSS changed from not listed to 6.5.
    • Added affected products: azl4 fido-device-onboard 0.5.5-13.azl4 on Azure Linux 4.0.
    • Added fixed versions: 0:0.5.5-13.azl4.

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.