Is virtualenv 21.14 vulnerable?
PyPI · 14 releases from 21.14.0 to 21.14.13 · latest virtualenv is 21.15.9 · checked 18 Nov 2026
No known advisories in the last release
virtualenv 21.14.13, the last 21.14 release, has no known advisories. 17 advisories affect earlier 21.14.x releases, so update to 21.14.13.
pip install 'virtualenv>=21.14.13'Is your project on an affected virtualenv?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 21.14.x, affecting earlier releases
virtualenv: Temporary app-data can leave dangling seed package links
- Affected
- >=21.14.8 <21.14.10
- Fixed in
- 21.14.10
virtualenv: Pip seeding with download omits wheel digest verification
- Affected
- <21.14.9
- Fixed in
- 21.14.9
virtualenv: Downloaded wheel selection and caching precede verification
- Affected
- <21.14.9
- Fixed in
- 21.14.9
virtualenv: Xonsh activation literals depend on the script decoding codec
- Affected
- <21.14.9
- Fixed in
- 21.14.9
virtualenv: Seeded files retain permissions from an older cache
- Affected
- <21.14.9
- Fixed in
- 21.14.9
virtualenv: Bash prompt values can change meaning under older compatibility modes
- Affected
- <21.14.9
- Fixed in
- 21.14.9
virtualenv: Venv configuration readback can reinterpret path boundaries
- Affected
- <21.14.9
- Fixed in
- 21.14.9
virtualenv: Seed replacement does not contain metadata deletion paths
- Affected
- <21.14.9
- Fixed in
- 21.14.9
virtualenv: Bash activator leaves the --prompt value unescaped in PS1 when promptvars is off, so prompt expansion later executes it (regression in 21.14.9)
- Affected
- >=21.14.9 <21.14.13
- Fixed in
- 21.14.13
virtualenv: Generated files can follow existing destination links
- Affected
- <21.14.9
- Fixed in
- 21.14.9
virtualenv: Builtin creation follows linked environment directories
- Affected
- <21.14.9
- Fixed in
- 21.14.9
virtualenv: Deletion recovery can change a symlink target's mode
- Affected
- <21.14.9
- Fixed in
- 21.14.9
virtualenv: Generated POSIX console launchers interpret destination paths as shell syntax
- Affected
- <21.14.9
- Fixed in
- 21.14.9
virtualenv bash activate runs commands from an environment name with a backslash before $
- Affected
- <21.14.7
- Fixed in
- 21.14.7
virtualenv activate runs commands from the environment name in zsh with PROMPT_SUBST
- Affected
- <21.14.4
- Fixed in
- 21.14.4
virtualenv activate.fish runs commands from a path or prompt with a backslash before a quote
- Affected
- <21.14.2
- Fixed in
- 21.14.2
virtualenv activation scripts run code from a path that contains a placeholder name
- Affected
- >=20.26.6 <21.14.2
- Fixed in
- 21.14.2
Every virtualenv 21.14.x release
Affected: 21.14.0 to 21.14.12. 21.14.13 is not affected. Latest virtualenv: 21.15.9.
| Version | Known advisories |
|---|---|
| virtualenv 21.14.13 | None |
| virtualenv 21.14.12 | CVE-2026-115586 |
| virtualenv 21.14.11 | CVE-2026-115586 |
| virtualenv 21.14.10 | CVE-2026-115586 |
| virtualenv 21.14.9 | CVE-2026-113713, CVE-2026-115586 |
| virtualenv 21.14.8 | CVE-2026-113713, CVE-2026-113717, CVE-2026-113714, CVE-2026-113718, CVE-2026-113720, CVE-2026-113723, CVE-2026-113715, CVE-2026-113719, CVE-2026-113721, CVE-2026-113716, CVE-2026-113724, CVE-2026-113722 |
| virtualenv 21.14.7 | CVE-2026-113717, CVE-2026-113714, CVE-2026-113718, CVE-2026-113720, CVE-2026-113723, CVE-2026-113715, CVE-2026-113719, CVE-2026-113721, CVE-2026-113716, CVE-2026-113724, CVE-2026-113722 |
| virtualenv 21.14.6 | CVE-2026-113717, CVE-2026-113714, CVE-2026-113718, CVE-2026-113720, CVE-2026-113723, CVE-2026-113715, CVE-2026-113719, CVE-2026-113721, CVE-2026-113716, CVE-2026-113724, CVE-2026-113722, CVE-2026-113725 |
| virtualenv 21.14.5 | CVE-2026-113717, CVE-2026-113714, CVE-2026-113718, CVE-2026-113720, CVE-2026-113723, CVE-2026-113715, CVE-2026-113719, CVE-2026-113721, CVE-2026-113716, CVE-2026-113724, CVE-2026-113722, CVE-2026-113725 |
| virtualenv 21.14.4 | CVE-2026-113717, CVE-2026-113714, CVE-2026-113718, CVE-2026-113720, CVE-2026-113723, CVE-2026-113715, CVE-2026-113719, CVE-2026-113721, CVE-2026-113716, CVE-2026-113724, CVE-2026-113722, CVE-2026-113725 |
| virtualenv 21.14.3 | CVE-2026-113717, CVE-2026-113714, CVE-2026-113718, CVE-2026-113720, CVE-2026-113723, CVE-2026-113715, CVE-2026-113719, CVE-2026-113721, CVE-2026-113716, CVE-2026-113724, CVE-2026-113722, CVE-2026-113725, CVE-2026-113726 |
| virtualenv 21.14.2 | CVE-2026-113717, CVE-2026-113714, CVE-2026-113718, CVE-2026-113720, CVE-2026-113723, CVE-2026-113715, CVE-2026-113719, CVE-2026-113721, CVE-2026-113716, CVE-2026-113724, CVE-2026-113722, CVE-2026-113725, CVE-2026-113726 |
| virtualenv 21.14.1 | CVE-2026-113717, CVE-2026-113714, CVE-2026-113718, CVE-2026-113720, CVE-2026-113723, CVE-2026-113715, CVE-2026-113719, CVE-2026-113721, CVE-2026-113716, CVE-2026-113724, CVE-2026-113722, CVE-2026-113725, CVE-2026-113726, CVE-2026-113732, CVE-2026-113776 |
| virtualenv 21.14.0 | CVE-2026-113717, CVE-2026-113714, CVE-2026-113718, CVE-2026-113720, CVE-2026-113723, CVE-2026-113715, CVE-2026-113719, CVE-2026-113721, CVE-2026-113716, CVE-2026-113724, CVE-2026-113722, CVE-2026-113725, CVE-2026-113726, CVE-2026-113732, CVE-2026-113776 |
Which of your client projects are still on virtualenv 21.14?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact virtualenv version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other virtualenv versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.