Virtual environment (venv) activation scripts don't quote paths
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 3.9.21, 3.10.16, 3.11.11 and 3 more.
A vulnerability has been found in the CPython `venv` module and CLI where path names provided when creating a virtual environment were not quoted properly, allowing the creator to inject commands into virtual environment "activation" scripts (ie "source venv/bin/activate"). This means that attacker-controlled virtual environments are able to run commands when the virtual environment is activated. Virtual environments which are not created by an attacker or which aren't activated before being used (ie "./venv/bin/python") are not affected.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Python Software Foundation | <3.9.21, >=3.10.0 <3.10.16, >=3.11.0 <3.11.11, >=3.12.0 <3.12.8, >=3.13.0 <3.13.1, >=3.14.0a1 <3.14.0a2 | 3.9.21, 3.10.16, 3.11.11, 3.12.8, 3.13.1, 3.14.0a2 |
Timeline
Every event on this vulnerability
Embed
A live severity badge for an advisory, README or ticket