VulertSecurity VulertSecurity

Vulnerability Database · PyPI · virtualenv · Version

virtualenv 21.3.2

21.3.2 is affected by 16 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 0 High 9 Medium 4 Low 0 Unrated 3

All virtualenv versions & vulnerabilities → Source repository Search the database for this package →
Released 12 May 2026 Licence MIT Also known from other sources 15 Newer releases 300 Database updated 23/Oct/2026

Release and licence data published by PyPI. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

virtualenv 21.3.2 vulnerabilities

16 vulnerabilities cover virtualenv 21.3.2. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2026-113722: virtualenv POSIX Console Launchers Vulnerability Leading to Shell Command Execution 7.8 high 21.14.9 21 Oct 2026
CVE-2026-113725: virtualenv Bash Activate Command Injection Vulnerability 7.8 high 21.14.7 21 Oct 2026
CVE-2026-113726: virtualenv Command Injection Vulnerability in zsh with PROMPT_SUBST 7.8 high 21.14.4 21 Oct 2026
CVE-2026-113732: virtualenv Command Injection Vulnerability in activate.fish 7.8 high 21.14.2 21 Oct 2026
CVE-2026-113776: virtualenv Activation Scripts Execute Arbitrary Code from Path Placeholders 7.8 high 21.14.2 21 Oct 2026
CVE-2026-102925: virtualenv Bash and Fish Activation Scripts Vulnerability 7.8 high 21.7.13 01 Oct 2026
CVE-2026-102925: virtualenv Bash and Fish Activation Scripts Command Execution Vulnerability 7.8 high 21.7.13 18 Sep 2026
CVE-2026-102930: virtualenv - Integrity Check Bypass for Downloaded Seed Wheels 7.7 high 21.7.12 30 Sep 2026
CVE-2026-102937: virtualenv Command Injection via --prompt in activate.bat 7.3 high 21.7.12 01 Oct 2026
CVE-2026-102938: virtualenv Configuration Injection via Unvalidated Prompt Values 5.8 medium 21.7.11 30 Sep 2026
CVE-2026-113721: virtualenv can write generated files through destination links 4.5 medium 21.14.9 22 Oct 2026
CVE-2026-113716: virtualenv Symlink Vulnerability Allows Unauthorized File Writes 4.5 medium 21.14.9 21 Oct 2026
CVE-2026-113724: virtualenv Symlink Target Mode Change on Deletion Recovery 4.5 medium 21.14.9 21 Oct 2026
CVE-2026-102930: Virtualenv Integrity Check Bypass in Downloaded Seed Wheels N/A unrated 21.7.12 18 Sep 2026
CVE-2026-102937: Command Injection Vulnerability in virtualenv's activate.bat N/A unrated 21.7.12 18 Sep 2026
CVE-2026-102938: virtualenv Configuration Injection via Unvalidated Prompt Values N/A unrated 21.7.11 17 Sep 2026

Looking for another version, or everything Vulert holds for virtualenv?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About virtualenv 21.3.2

Is virtualenv 21.3.2 vulnerable?

Yes. 16 vulnerabilities in the Vulert database cover virtualenv 21.3.2: 0 critical, 9 high, 4 medium and 0 low, plus 3 not yet rated. Each entry above names the fixed version to move to.

Is 21.3.2 the latest release of virtualenv?

No. 21.3.2 was published 12 May 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor virtualenv for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the virtualenv version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.