Microsoft security update for CVE-2026-6357
🔗 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-6357. This page also shows what EchelonGraph holds for CVE-2026-6357, 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 products8
- 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 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: 3 updates
3 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.
| KB article | Update | Fixed build |
|---|---|---|
| — | Security Update | 24.2-8 |
| — | Security Update | 20.36.1-4 |
| — | Security Update | — |
🧭 EchelonGraph on CVE-2026-6357
- EchelonGraph score
- 5.3 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 prior to version 26.1 would run self-update check functionality after installing wheel files which required importing well-known Python modules names. These module imports were intentionally deferred to increase startup time of the pip CLI. The patch changes self-update functionality to run before wheels are installed to prevent newly-installed modules from being imported shortly after the installation of a wheel package. Users should still review package contents prior to installation.
Published by Python Software Foundation, the CVE Numbering Authority that assigned CVE-2026-6357, 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).