CVE-2026-22702: virtualenv Has TOCTOU Vulnerabilities in Directory Creation

Published Jan 10, 2026
·
Updated

Impact

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 appdata and lock file operations to attacker-controlled locations.

Affected versions: All versions up to and including 20.36.1

Affected users: Any user running virtualenv on multi-user systems where untrusted local users have filesystem access to shared temporary directories or where VIRTUALENVOVERRIDEAPPDATA points to a user-writable location.

Attack scenarios: - Cache poisoning: Attacker corrupts wheels or Python metadata in the cache - Information disclosure: Attacker reads sensitive cached data or metadata - Lock bypass: Attacker controls lock file semantics to cause concurrent access violations - Denial of service: Lock starvation preventing virtualenv operations

Patches

The vulnerability has been patched by replacing check-then-act patterns with atomic os.makedirs(..., existok=True) operations.

Fixed in: PR #3013

Versions with the fix: 20.36.2 and later

Users should upgrade to version 20.36.2 or later.

Workarounds

If you cannot upgrade immediately:

1. Ensure VIRTUALENVOVERRIDEAPPDATA points to a directory owned by the current user with restricted permissions (mode 0700) 2. Avoid running virtualenv in shared temporary directories where other users have write access 3. Use separate user accounts for different projects to isolate appdata directories

References

- GitHub PR: https://github.com/pypa/virtualenv/pull/3013 - Vulnerability reported by: @tsigouris007 - CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization (TOCTOU) - CWE-59: Improper Link Resolution Before File Access

Other sources

virtualenv Has TOCTOU Vulnerabilities in Directory Creation

Microsoft

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 appdata and lock file operations to attacker-controlled locations. This issue has been patched in version 20.36.1.

MITRE

Affected Software

6 affected componentsFixes available
pypi/virtualenv<20.36.1
pip/virtualenv<20.36.1
20.36.1
virtualenv virtualenv<20.36.1
Microsoft cbl2 python-virtualenv 20.26.6-2<20.36.1-1
20.36.1-1
Microsoft cbl2 python-virtualenv 20.26.6-3<20.36.1-1
20.36.1-1
Microsoft azl3 python-virtualenv 20.25.0-3<20.36.1-1
20.36.1-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/virtualenv to a version that resolves this vulnerability.

    Fixed in 20.36.1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 20.36.1-1
  3. Upgrade

    Upgrade virtualenv to a version that resolves this vulnerability.

    Fixed in 20.36.2
  4. Configuration

    Set VIRTUALENV_OVERRIDE_APP_DATA to a directory owned by the current user and restrict its permissions to mode 0700 (and avoid shared/writable locations).

    virtualenv VIRTUALENV_OVERRIDE_APP_DATA = directory owned by current user with restricted permissions (mode 0700)
  5. Compensating control

    Avoid running virtualenv in shared temporary directories where other users have filesystem write access.

Event History

Jan 10, 2026
CVE Published
via MITRE·06:05 AM
Data Sourced
via MITRE·06:05 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
RemedyAffected Software
Jan 13, 2026
Data Sourced
via Microsoft·09:02 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·09:02 AM
Affected Software
Updated
via Microsoft·09:02 AM
Affected Software
Updated
via Microsoft·09:02 AM
DescriptionSeverity
Advisory Published
via GitHub·06:45 PM
Data Sourced
via GitHub·06:45 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-22702?

CVE-2026-22702 is classified as a moderate severity vulnerability due to its ability to allow local attackers to exploit symlink-based attacks.

2

How do I fix CVE-2026-22702?

To fix CVE-2026-22702, upgrade virtualenv to version 20.36.1 or later.

3

Who is affected by CVE-2026-22702?

CVE-2026-22702 affects users of virtualenv prior to version 20.36.1.

4

What type of vulnerability is CVE-2026-22702?

CVE-2026-22702 is a TOCTOU (Time-of-Check-Time-of-Use) vulnerability.

5

What kind of attacks can CVE-2026-22702 facilitate?

CVE-2026-22702 can facilitate local symlink-based attacks during directory creation operations.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203