CVE-2026-33055Medium

Microsoft security update for CVE-2026-33055

Published
May 31, 2026
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33055. This page also shows what EchelonGraph holds for CVE-2026-33055, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products19

  • azl3 clamav 1.5.2-1 on Azure Linux 3.0
  • azl3 clamav 1.5.2-2 on Azure Linux 3.0
  • azl3 kata-containers-cc 3.15.0.aks0-7 on Azure Linux 3.0
  • azl3 kata-containers-cc 3.15.0.aks0-8 on Azure Linux 3.0
  • azl3 rpm-ostree 2024.4-10 on Azure Linux 3.0
  • azl3 rpm-ostree 2024.4-6 on Azure Linux 3.0
  • azl3 rpm-ostree 2024.4-8 on Azure Linux 3.0
  • azl3 rust 1.75.0-25 on Azure Linux 3.0
  • azl3 rust 1.75.0-27 on Azure Linux 3.0
  • azl3 rust 1.90.0-4 on Azure Linux 3.0
  • azl3 rust 1.90.0-6 on Azure Linux 3.0
  • azl3 trident 0.21.0-1 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
  • cbl2 rpm-ostree 2022.1-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
  • cbl2 rust 1.72.0-15 on CBL Mariner 2.0
  • cbl2 rust 1.72.0-15 on CBL-Mariner 2.0

✅ Updates Microsoft lists: 7 updates

7 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update2022.1-9
—Security Update0.22.0-1
—Security Update1.72.0-16
—Security Update1.75.0-28
—Security Update1.90.0-7
—Security Update2024.4-10
—Security Update1.5.2-2

🧭 EchelonGraph on CVE-2026-33055

EchelonGraph score
8.1 HIGH
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

tar-rs is a tar archive reading/writing library for Rust. Versions 0.4.44 and below have conditional logic that skips the PAX size header in cases where the base header size is nonzero. As part of CVE-2025-62518, the astral-tokio-tar project was changed to correctly honor PAX size headers in the case where it was different from the base header. This is almost the inverse of the astral-tokio-tar issue. Any discrepancy in how tar parsers honor file size can be used to create archives that appear differently when unpacked by different archivers. In this case, the tar-rs (Rust tar) crate is an outlier in checking for the header size - other tar parsers (including e.g. Go archive/tar) unconditionally use the PAX size override. This can affect anything that uses the tar crate to parse archives and expects to have a consistent view with other parsers. This issue has been fixed in version 0.4.45.

Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2026-33055, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)