Virtualenv: From 20.26.6 until 21.14.2, ViaTemplateActivator.instantiate_template() replaces placeholders one key at a
Affects virtualenvSource GCVE Database
Not known to be exploited · CVSS 7.8 High : upgrade to 21.14.2 soon.
Data as of 18 Nov 2026, 13:06 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.8 |
|---|
- Patch
- Available – fixed in 21.14.2
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade virtualenv to 21.14.2.
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIvirtualenvpkg:pypi/virtualenvOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade virtualenv to version 21.14.2 or later, where this vulnerability is fixed. The vendor has released patches and security advisories detailing the fix. No other mitigations are indicated or required if the upgrade is applied.
Description
Virtualenv versions from 20.26.6 up to but not including 21.14.2 contain a vulnerability in the ViaTemplateActivator.instantiate_template() method. This method replaces placeholders in activation templates one key at a time, allowing certain placeholder names to be replaced multiple times during activation. This behavior can lead to command execution when activating the environment via bash, fish, xonsh, or activate_this.py if an attacker can control the destination path or --prompt value. The issue is fixed in version 21.14.2.