virtualenv vulnerabilities
Virtual Python Environment builder
- Registry
- PyPI
- Latest
- 21.15.9
- License
- MIT
24 known advisories
The latest version, 21.15.9, is not affected by any of them. Projects on older versions may be.
pip install 'virtualenv>=21.15.9'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
Security advisories for virtualenv
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
virtualenv bash and fish activation scripts execute commands embedded in paths
- Affected
- <21.7.13
- Fixed in
- 21.7.13
virtualenv: Command injection via --prompt in activate.bat (batch activator)
- Affected
- <21.7.12
- Fixed in
- 21.7.12
virtualenv: Downloaded seed wheels (pip/setuptools) are not integrity-checked before use
- Affected
- <21.7.12
- Fixed in
- 21.7.12
virtualenv writes prompt values into pyvenv.cfg without sanitizing line boundaries, allowing configuration injection
- Affected
- <21.7.11
- Fixed in
- 21.7.11
virtualenv Has TOCTOU Vulnerabilities in Directory Creation
- Affected
- <20.36.1
- Fixed in
- 20.36.1
virtualenv allows command injection through activation scripts for a virtual environment
- Affected
- <20.26.6
- Fixed in
- 20.26.6
Virtualenv Allows Symlink Attack on /tmp/
- Affected
- <1.5
- Fixed in
- 1.5
Is your virtualenv version vulnerable?
- virtualenv 21.15No known advisories in 21.15.9
- virtualenv 21.14No known advisories in 21.14.13
- virtualenv 21.1315 advisories in 21.13.0
- virtualenv 21.1215 advisories in 21.12.1
- virtualenv 21.1115 advisories in 21.11.1
- virtualenv 21.1015 advisories in 21.10.0
- virtualenv 20.3919 advisories in 20.39.1
- virtualenv 20.3819 advisories in 20.38.0
- virtualenv 20.3619 advisories in 20.36.1
- virtualenv 20.3520 advisories in 20.35.4
- virtualenv 20.3420 advisories in 20.34.0
- virtualenv 20.3320 advisories in 20.33.1
- virtualenv 16.720 advisories in 16.7.12
- virtualenv 16.620 advisories in 16.6.2
- virtualenv 16.520 advisories in 16.5.0
- virtualenv 16.420 advisories in 16.4.3
- virtualenv 16.320 advisories in 16.3.0
- virtualenv 16.220 advisories in 16.2.0
Which of your client projects still run an old virtualenv?
NPMscan reads the requirements.txt, poetry.lock, uv.lock and Pipfile.lock in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other PyPI packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the PyPI registry.