CVE-2026-3219Medium

Microsoft security update for CVE-2026-3219

Published
June 2, 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-3219. This page also shows what EchelonGraph holds for CVE-2026-3219, 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 products9

  • azl3 python-pip 24.2-6 on Azure Linux 3.0
  • azl3 python-pip 24.2-8 on Azure Linux 3.0
  • azl3 python-virtualenv 20.36.1-2 on Azure Linux 3.0
  • azl3 python-virtualenv 20.36.1-4 on Azure Linux 3.0
  • cbl2 python-virtualenv 20.26.6-3
  • cbl2 python-virtualenv 20.26.6-3 on CBL Mariner 2.0
  • cbl2 python-virtualenv 20.26.6-3 on CBL-Mariner 2.0
  • cbl2 python3 3.9.19-19 on CBL Mariner 2.0
  • cbl2 python3 3.9.19-19 on CBL-Mariner 2.0

✅ Updates Microsoft lists: 5 updates

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

KB articleUpdateFixed build
—Security Update24.2-7
—Security Update20.36.1-3
—Security Update20.36.1-4
—Security Update24.2-8
—Security Update—

🧭 EchelonGraph on CVE-2026-3219

EchelonGraph score
4.6 MEDIUM
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

pip handles concatenated tar and ZIP files as ZIP files regardless of filename or whether a file is both a tar and ZIP file. This behavior could result in confusing installation behavior, such as installing "incorrect" files according to the filename of the archive. New behavior only proceeds with installation if the file identifies uniquely as a ZIP or tar archive, not as both.

Published by Python Software Foundation, the CVE Numbering Authority that assigned CVE-2026-3219, 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)