VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

virtualenv: vulnerability history, versions and safety

virtualenv is a package in the PyPI ecosystem. Vulert records 22 vulnerabilities for it across 116 releases, from Dec 2011 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
22 vulnerabilities recorded H9 M6 U7
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
18 in the last 12 months

Most recent disclosure 22 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all virtualenv vulnerabilities

Vulert verdict on virtualenv 21.14.12 i

Updated on 23 Oct 2026

Good news: 21.14.12, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 22.

Package health score 61/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Not enough data

What to do: Stay on 21.14.12 or newer. This can change: a vulnerability disclosed tomorrow can affect 21.14.12 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 21.14.12 — unaffected i
  • Vulnerabilities on record 22 over 14 years · 18 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 3,602 packages i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for virtualenv, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
21.14.12 21 Oct 2026 none MIT — Details →
21.14.11 18 Oct 2026 none MIT — Details →
21.14.10 17 Oct 2026 none MIT — Details →
21.14.9 17 Oct 2026 none MIT — Details →
21.14.8 16 Oct 2026 H1 M3 MIT Yes Details →
21.14.7 12 Oct 2026 H1 M3 MIT Yes Details →
21.14.6 08 Oct 2026 H2 M3 MIT Yes Details →
21.14.5 02 Oct 2026 H2 M3 MIT Yes Details →
21.14.4 02 Oct 2026 H2 M3 MIT Yes Details →
21.14.3 01 Oct 2026 H3 M3 MIT Yes Details →
21.14.2 01 Oct 2026 H3 M3 MIT Yes Details →
21.14.1 29 Sep 2026 H5 M3 MIT Yes Details →
21.14.0 29 Sep 2026 H5 M3 MIT Yes Details →
21.13.0 26 Sep 2026 H5 M3 MIT Yes Details →
21.12.1 24 Sep 2026 H5 M3 MIT Yes Details →
21.12.0 24 Sep 2026 H5 M3 MIT Yes Details →
21.11.1 23 Sep 2026 H5 M3 MIT Yes Details →
21.11.0 23 Sep 2026 H5 M3 MIT Yes Details →
21.10.0 22 Sep 2026 H5 M3 MIT Yes Details →
21.9.1 22 Sep 2026 H5 M3 MIT Yes Details →
21.9.0 20 Sep 2026 H5 M3 MIT Yes Details →
21.8.1 19 Sep 2026 H5 M3 MIT Yes Details →
21.7.16 19 Sep 2026 H5 M3 MIT Yes Details →
21.7.15 18 Sep 2026 H5 M3 MIT Yes Details →
21.7.14 18 Sep 2026 H5 M3 MIT Yes Details →
21.7.13 18 Sep 2026 H5 M3 MIT Yes Details →
21.7.12 18 Sep 2026 H6 M3 U1 MIT Yes Details →
21.7.11 17 Sep 2026 H8 M3 U3 MIT Yes Details →
21.7.10 15 Sep 2026 H8 M4 U4 MIT Yes Details →
21.7.9 09 Sep 2026 H8 M4 U4 MIT Yes Details →
21.7.8 01 Sep 2026 H8 M4 U4 MIT Yes Details →
21.7.7 28 Aug 2026 H8 M4 U4 MIT Yes Details →
21.7.6 28 Aug 2026 H8 M4 U4 MIT Yes Details →
21.7.5 25 Aug 2026 H8 M4 U4 MIT Yes Details →
21.7.4 10 Aug 2026 H8 M4 U4 MIT Yes Details →
21.7.3 08 Aug 2026 H8 M4 U4 MIT Yes Details →
21.7.2 07 Aug 2026 H8 M4 U4 MIT Yes Details →
21.7.1 30 Jul 2026 H8 M4 U4 MIT Yes Details →
21.7.0 21 Jul 2026 H8 M4 U4 MIT Yes Details →
21.6.1 10 Jul 2026 H8 M4 U4 MIT Yes Details →
21.6.0 06 Jul 2026 H8 M4 U4 MIT Yes Details →
21.5.2 06 Jul 2026 H8 M4 U4 MIT Yes Details →
21.5.1 16 Jun 2026 H8 M4 U4 MIT Yes Details →
21.5.0 13 Jun 2026 H8 M4 U4 MIT Yes Details →
21.4.3 11 Jun 2026 H8 M4 U4 MIT Yes Details →
21.4.2 31 May 2026 H8 M4 U4 MIT Yes Details →
21.4.1 28 May 2026 H8 M4 U4 MIT Yes Details →
21.4.0 28 May 2026 H8 M4 U4 MIT Yes Details →
21.3.3 13 May 2026 H8 M4 U4 MIT Yes Details →
21.3.2 12 May 2026 H8 M4 U4 MIT Yes Details →
21.3.1 05 May 2026 H8 M4 U4 MIT Yes Details →
21.3.0 27 Apr 2026 H8 M4 U4 MIT Yes Details →
21.2.4 14 Apr 2026 H8 M4 U4 MIT Yes Details →
21.2.3 14 Apr 2026 H8 M4 U4 MIT Yes Details →
21.2.2 13 Apr 2026 H8 M4 U4 MIT Yes Details →
21.2.1 09 Apr 2026 H8 M4 U4 MIT Yes Details →
21.2.0 09 Mar 2026 H8 M4 U4 MIT Yes Details →
21.1.0 27 Feb 2026 H8 M4 U4 MIT Yes Details →
21.0.0 25 Feb 2026 H8 M4 U4 MIT Yes Details →
20.39.1 25 Feb 2026 H8 M4 U4 MIT Yes Details →
20.39.0 23 Feb 2026 H8 M4 U4 MIT Yes Details →
20.38.0 19 Feb 2026 H8 M4 U4 MIT Yes Details →
20.36.1 09 Jan 2026 H8 M4 U4 MIT Yes Details →
20.36.0 07 Jan 2026 H8 M5 U5 MIT Yes Details →
20.35.4 29 Oct 2025 H8 M5 U5 MIT Yes Details →
20.35.3 10 Oct 2025 H8 M5 U5 MIT Yes Details →
20.35.2 10 Oct 2025 H8 M5 U5 MIT Yes Details →
20.35.1 09 Oct 2025 H8 M5 U5 MIT Yes Details →
20.35.0 08 Oct 2025 H8 M5 U5 MIT Yes Details →
20.34.0 13 Aug 2025 H8 M5 U5 MIT Yes Details →
20.33.1 05 Aug 2025 H8 M5 U5 MIT Yes Details →
20.33.0 03 Aug 2025 H8 M5 U5 MIT Yes Details →
20.32.0 21 Jul 2025 H8 M5 U5 MIT Yes Details →
20.31.2 08 May 2025 H8 M5 U5 MIT Yes Details →
20.31.1 05 May 2025 H8 M5 U5 MIT Yes Details →
20.31.0 05 May 2025 H8 M5 U5 MIT Yes Details →
20.30.0 31 Mar 2025 H8 M5 U5 MIT Yes Details →
20.29.3 06 Mar 2025 H8 M5 U5 MIT Yes Details →
20.29.2 10 Feb 2025 H8 M5 U5 MIT Yes Details →
20.29.1 17 Jan 2025 H8 M5 U5 MIT Yes Details →
20.29.0 15 Jan 2025 H8 M5 U5 MIT Yes Details →
20.28.1 03 Jan 2025 H8 M5 U5 MIT Yes Details →
20.28.0 26 Nov 2024 H8 M5 U5 MIT Yes Details →
20.27.1 28 Oct 2024 H8 M5 U5 MIT Yes Details →
20.27.0 18 Oct 2024 H8 M5 U5 MIT Yes Details →
20.26.6 27 Sep 2024 H8 M5 U5 MIT Yes Details →
20.26.5 17 Sep 2024 H8 M5 U6 MIT Yes Details →
20.26.4 07 Sep 2024 H8 M5 U6 MIT Yes Details →
20.26.3 22 Jun 2024 H8 M5 U6 MIT Yes Details →
20.26.2 13 May 2024 H8 M5 U6 MIT Yes Details →
20.26.1 29 Apr 2024 H8 M5 U6 MIT Yes Details →
20.26.0 23 Apr 2024 H8 M5 U6 MIT Yes Details →
20.25.3 17 Apr 2024 H8 M5 U6 MIT Yes Details →
20.25.2 17 Apr 2024 H8 M5 U6 MIT Yes Details →
20.25.1 22 Feb 2024 H8 M5 U6 MIT Yes Details →
20.25.0 01 Dec 2023 H8 M5 U6 MIT Yes Details →
20.24.7 21 Nov 2023 H8 M5 U6 MIT Yes Details →
20.24.6 23 Oct 2023 H8 M5 U6 MIT Yes Details →
20.24.5 08 Sep 2023 H8 M5 U6 MIT Yes Details →
20.24.4 30 Aug 2023 H8 M5 U6 MIT Yes Details →
20.24.3 11 Aug 2023 H8 M5 U6 — Yes Details →
20.24.2 24 Jul 2023 H8 M5 U6 — Yes Details →
20.24.1 20 Jul 2023 H8 M5 U6 — Yes Details →
20.24.0 14 Jul 2023 H8 M5 U6 — Yes Details →
20.23.1 16 Jun 2023 H8 M5 U6 — Yes Details →
20.23.0 27 Apr 2023 H8 M5 U6 — Yes Details →
20.22.0 19 Apr 2023 H8 M5 U6 — Yes Details →
20.21.1 19 Apr 2023 H8 M5 U6 — Yes Details →
20.21.0 12 Mar 2023 H8 M5 U6 — Yes Details →
20.20.0 28 Feb 2023 H8 M5 U6 — Yes Details →
20.19.0 07 Feb 2023 H8 M5 U6 — Yes Details →
20.18.0 06 Feb 2023 H8 M5 U6 — Yes Details →
20.17.1 05 Dec 2022 H8 M5 U6 — Yes Details →
20.17.0 28 Nov 2022 H8 M5 U6 — Yes Details →
20.16.7 12 Nov 2022 H8 M5 U6 — Yes Details →
20.16.6 25 Oct 2022 H8 M5 U6 — Yes Details →
20.16.5 08 Sep 2022 H8 M5 U6 — Yes Details →
20.16.4 30 Aug 2022 H8 M5 U6 — Yes Details →
20.16.3 04 Aug 2022 H8 M5 U6 — Yes Details →
20.16.2 27 Jul 2022 H8 M5 U6 — Yes Details →

The newest 120 of 340 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2011 1
  • 2022 1
  • 2024 2
  • 2026 18

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 18 of the 22 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for virtualenv

The 5 most severe of 22 vulnerabilities recorded for this package

Search all 22 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-53899: Command Injection Vulnerability in virtualenv Prior to 20.26.6 9.8 critical 20.26.6 24 Nov 2024
CVE-2024-53899: Command Injection Vulnerability in virtualenv 8.4 high 20.26.6 24 Nov 2024
CVE-2026-113722: virtualenv POSIX Console Launchers Vulnerability Leading to Shell Command Execution 7.8 high 21.14.9 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-102925: virtualenv Bash and Fish Activation Scripts Vulnerability 7.8 high 21.7.13 01 Oct 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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

Is virtualenv safe to use?

Vulert records 22 vulnerabilities for virtualenv in PyPI: 0 critical, 9 high, 6 medium and 0 low, plus 7 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is virtualenv's Vulert package health score?

Vulert scores virtualenv 61/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of virtualenv affected?

No. 21.14.12, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does virtualenv have?

22 vulnerabilities are recorded for virtualenv in the PyPI ecosystem: 0 critical, 9 high, 6 medium and 0 low, plus 7 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new virtualenv vulnerabilities disclosed?

18 vulnerabilities were recorded for virtualenv in the last 12 months, and the oldest entry in this database dates to 31 Dec 2011. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of virtualenv are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.