CVE-2026-22702MediumMicrosoft CVSS 4.5CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

Microsoft security update for CVE-2026-22702

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-22702. This page also shows what EchelonGraph holds for CVE-2026-22702, 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 products4

  • azl3 python-virtualenv 20.25.0-3 on Azure Linux 3.0
  • cbl2 python-virtualenv 20.26.6-2 on CBL Mariner 2.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

✅ Updates Microsoft lists: 1 update

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

KB articleUpdateFixed build
—Security Update20.36.1-1

🧭 EchelonGraph on CVE-2026-22702

EchelonGraph score
4.5 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

virtualenv is a tool for creating isolated virtual python environments. Prior to version 20.36.1, TOCTOU (Time-of-Check-Time-of-Use) vulnerabilities in virtualenv allow local attackers to perform symlink-based attacks on directory creation operations. An attacker with local access can exploit a race condition between directory existence checks and creation to redirect virtualenv's app_data and lock file operations to attacker-controlled locations. This issue has been patched in version 20.36.1.

Published by GitHub, Inc., the CVE Numbering Authority that assigned CVE-2026-22702, 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)