https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 22 Oct 2026 14:42:38 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-113725 <p>virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.7, the bash activate script escapes the environment name for only one of the two passes bash makes over PS1, so a backslash in the name undoes the escaping and a name containing \$(...) runs as commands in the user&#39;s shell each time bash draws the prompt. This issue is fixed in version 21.14.7.</p> <p>virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.7, the bash activate script escapes the environment name for only one of the two passes bash makes over PS1, so a backslash in the name undoes the escaping and a name containing \$(...) runs as commands in the user&#39;s shell each time bash draws the prompt. This issue is fixed in version 21.14.7.</p> https://db.gcve.eu/vuln/fkie_cve-2026-113725 https://db.gcve.eu/vuln/ghsa-vxj4-q4g9-crj7 <p><strong>Affected:</strong> PyPI: virtualenv</p> <p>### Summary</p> <p>The bash `activate` script escapes the environment name for only one of the two passes bash makes over `PS1`, so a backslash in the name undoes the escaping and a name containing `\$(...)` runs as commands in the user&#39;s shell each time bash draws the prompt.</p> <p>### Affected area</p> <p>`src/virtualenv/activation/bash/activate.sh`, the block that prepends the environment name to `PS1`.</p> <p>### Attacker-controlled input</p> <p>The environment name: the environment directory&#39;s name, or the `--prompt` or `VIRTUALENV_PROMPT` value. An attacker needs to influence it, for example through a CI job or wrapper tool that passes a branch, project or job name through, or a directory in a cloned repository or unpacked archive. `--prompt .` takes the current directory&#39;s name.</p> <p>### Details</p> <p>bash handles `PS1` in two passes each time it draws the prompt: it first decodes backslash prompt escapes, turning `\\` into `\` and `\$` into `$` (or `#` for root), and then runs parameter expansion, command substitution and arithmetic expansion on the result. Since 21.13.0 the script escapes backslashes, dollar signs and backticks in the name, but only for the second pass, so the decode pass strips the escaping that a backslash in the name precedes. Releases before 21.13.0 do not escape the name at all. A bash running as root decodes `\$` to `#`, so the payload shows the wrong text there but runs nothing. zsh does no decode pass and is not affected.</p> <p>### Proof of concept</p> <p>```console $ virtualenv --prompt &#39;…</p> <p><strong>Affected:</strong> PyPI: virtualenv</p> <p>### Summary</p> <p>The bash `activate` script escapes the environment name for only one of the two passes bash makes over `PS1`, so a backslash in the name undoes the escaping and a name containing `\$(...)` runs as commands in the user&#39;s shell each time bash draws the prompt.</p> <p>### Affected area</p> <p>`src/virtualenv/activation/bash/activate.sh`, the block that prepends the environment name to `PS1`.</p> <p>### Attacker-controlled input</p> <p>The environment name: the environment directory&#39;s name, or the `--prompt` or `VIRTUALENV_PROMPT` value. An attacker needs to influence it, for example through a CI job or wrapper tool that passes a branch, project or job name through, or a directory in a cloned repository or unpacked archive. `--prompt .` takes the current directory&#39;s name.</p> <p>### Details</p> <p>bash handles `PS1` in two passes each time it draws the prompt: it first decodes backslash prompt escapes, turning `\\` into `\` and `\$` into `$` (or `#` for root), and then runs parameter expansion, command substitution and arithmetic expansion on the result. Since 21.13.0 the script escapes backslashes, dollar signs and backticks in the name, but only for the second pass, so the decode pass strips the escaping that a backslash in the name precedes. Releases before 21.13.0 do not escape the name at all. A bash running as root decodes `\$` to `#`, so the payload shows the wrong text there but runs nothing. zsh does no decode pass and is not affected.</p> <p>### Proof of concept</p> <p>```console $ virtualenv --prompt &#39;…</p> https://db.gcve.eu/vuln/ghsa-vxj4-q4g9-crj7