CVE-2026-113723: virtualenv: Bash prompt values can change meaning under older compatibility modes
virtualenv before 21.14.9 writes the environment prompt into `PS1` in a way that some shells expand again as a command. A prompt like `x$(touch MARKER)y` then runs when the prompt is drawn in dash, or in bash at compatibility level 4.2 or lower. Upgrade to virtualenv 21.14.9.
Published Oct 23, 2026 · Analysis Nov 1, 2026
What an attacker can do
bin/activate copies the environment prompt into PS1, and a shell expands PS1 again each time it draws a prompt. The value therefore has to survive the assignment and the later expansion. The bash and zsh branches escape for their usual rules, but three paths still treat prompt data as commands: dash sourcing activate directly, a child dash that inherits an exported PS1 from bash, and bash running at compatibility level 4.2 or lower.
The attacker must control the prompt or destination value passed to virtualenv, for example text that tox, hatch or another tool relays as --prompt. Creating the environment runs nothing. The payload fires later, when the user activates the environment and a shell draws the prompt. The child-dash path can arise after another environment's activation has exported PS1. The result is command execution with the user's privileges. The CVSS 4.0 vector reflects the local setting, high complexity and required user action. The advisory does not claim every POSIX shell or bash mode is affected.
Who is affected
Affected: virtualenv < 21.14.9; the maintainer-confirmed release is 21.14.8, and the first affected version is not established. The report traces direct dash sourcing to 20.0.0b1 and the inherited PS1 case to a change first released in 21.14.7. The bash 4.2 case was shown on bash 5.2. You are exposed only if outsiders can influence the --prompt or destination value.
pip show virtualenv
virtualenv --versionvirtualenv
- Ecosystem
- PyPI
- Affected
- < 21.14.9
- Fixed in
- 21.14.9
- Check
pip show virtualenv
How to fix it
Upgrade to virtualenv 21.14.9.
pip install --upgrade "virtualenv>=21.14.9"Per the release notes, the activation script no longer changes PS1 in shells other than bash and zsh, and VIRTUAL_ENV_PROMPT remains available there. In bash the prompt stays literal under older compatibility levels, with promptvars disabled and in posix mode. The release notes do not say that bash scripts must be regenerated, but recreating environments with 21.14.9 is the safe route.
Workarounds from the advisory: use trusted prompt and destination values, and on older releases set VIRTUAL_ENV_DISABLE_PROMPT=1.
How to tell if you were hit
Inspect bin/activate in your environments and look at the prompt text near the PS1 assignment. A $( or backticks inside it, from a prompt you did not write, is suspect. Check the wrappers that build --prompt values and whether they accept untrusted text, such as a branch or project name. Unexpected files or processes that appear when you activate an environment or open a nested sh are signs of exploitation. Check $BASH_COMPAT and whether PS1 is exported in your shell.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Summary
Caller-supplied prompt text can become executable syntax in the bash activation prompt. An attacker must influence the value passed to virtualenv, and a user must subsequently activate the environment and draw the prompt.
Affected area
Bash runs with compatibility level 4.2 and draws the environment prompt. Its replacement-string behavior differs from newer compatibility modes, leaving prompt text subject to a second interpretation. The report concerns POSIX activation. It does not establish exposure through unrelated activators.
Attacker-controlled input
The attacker controls prompt or destination data passed as a virtualenv argument. The user later sources the generated activation script.
Affected code
The relevant 21.14.8 source is in bash prompt assembly.
Mechanism
bin/activate copies the prompt into PS1. A shell expands PS1 again when it draws a prompt, so the value must survive both the assignment and that later expansion. The bash and zsh branches escape for their usual prompt rules. Three other paths still interpret prompt data as commands: dash sourcing activate directly, a child dash inheriting an exported PS1 from bash, and bash running at compatibility level 4.2 or lower. A value such as x$(touch MARKER)y then runs touch on prompt display. Creating the environment does not run the payload.
Reproduction and evidence
The scanner's child-shell reproducer creates an environment with --prompt 'x$(touch MARKER)y', sources bin/activate in interactive bash, and starts interactive sh (dash). Its control leaves PS1 unexported: neither shell creates MARKER. With PS1 exported, bash displays the prompt without executing the value, but the child dash creates MARKER; the reproducer ends in BUG. The report gives separate console reproductions for direct dash activation and bash compatibility level 4.2. The child-shell path can arise after another environment's activation has exported PS1.
The scanner linked this finding to #3326 and its follow-up #3390. Those changes cover the usual bash path but leave the three paths above. The proposed change in #3418 keeps a variable reference in PS1, so prompt text is expanded as data when drawn. The private report's reproducer was run by the scanner; the later command-execution result was supplied by the maintainer review. This advisory does not claim that every POSIX shell or every bash mode is affected.
Introduced
The report traces direct dash sourcing to the first 20.x activator (20.0.0b1), and inherited PS1 to #3390 (first released in 21.14.7). It demonstrates the compatibility-level case on bash 5.2. Those historical boundaries come from the report; the release confirmed by the maintainer is 21.14.8.
Attack sequence
sequenceDiagram
participant A as Prompt supplier
participant V as virtualenv
participant B as Interactive bash
participant D as Child dash
A->>V: --prompt x$(touch MARKER)y
V->>B: generated bin/activate
B->>B: assign escaped prompt to PS1
alt PS1 is not exported
B->>D: start sh with its own PS1
D-->>B: marker absent
else PS1 is exported
B->>D: start sh with inherited PS1
D->>D: expand $(touch MARKER) on prompt draw
D-->>B: marker created
endReproducer files
The following files are from the scanner report for ANT-2026-1MOI2X3T. They were tested against commit a857a7823c73 in the scanner image. The repro entrypoint expects companion files under /tmp/repro.d; cases that change user IDs need a disposable root-capable container. The last output line is BUG when the reported behavior occurs. These files are included as evidence and were not rerun for this advisory update.
`repro`
#!/usr/bin/env python3
import shutil
import subprocess
from pathlib import Path
work = Path("/tmp/repro-inherited-ps1")
shutil.rmtree(work, ignore_errors=True)
work.mkdir()
marker = work / "MARKER"
print("sh is", Path("/bin/sh").resolve())
# attacker: only the text a tool such as tox or hatch relays as --prompt
hostile_prompt = f"x$(touch {marker})y"
# set up: the environment, made with the virtualenv command
subprocess.run(
["virtualenv", "--no-periodic-update", "--without-pip", "--activators", "bash",
"--prompt", hostile_prompt, str(work / "env")],
check=True, stdout=subprocess.DEVNULL,
)
assert not marker.exists(), "creating the environment must not run the prompt"
# user: in an interactive bash, source bin/activate, then start sh.
# -i makes both shells draw their prompt although stdin is not a terminal; sh draws one, reads EOF and returns
session = Path("/tmp/repro.d/user_session.sh").read_text()
interactive_bash = ["bash", "--norc", "--noprofile", "-i"]
# control: PS1 set in bash but not exported, so sh does not inherit it
control = subprocess.run(interactive_bash, input="PS1='\\$ '\n" + session,
stderr=subprocess.PIPE, text=True, check=True)
print(control.stderr)
ran_in_control = marker.exists()
print("CONTROL PS1 not exported: marker created:", ran_in_control)
# attack: the same session with the one difference that PS1 is exported
attack = subprocess.run(interactive_bash, input="export PS1='\\$ '\n" + session,
stderr=subprocess.PIPE, text=True, check=True)
print(attack.stderr)
ran_in_attack = marker.exists()
print("OBSERVED PS1 exported: marker created:", ran_in_attack)
# check: the prompt text must be drawn, never run, by every shell that draws it
print("BUG" if ran_in_attack and not ran_in_control else "OK")`repro.d/user_session.sh`
. /tmp/repro-inherited-ps1/env/bin/activate
sh -i </dev/nullImpact
An affected activation can execute commands with the user's privileges. Severity is high, following the generated-script precedent in GHSA-p58f-9548-mpm2. The attack requires control of argument data and subsequent user activation; it does not require replacing an executable or controlling app-data contents.
Versions tested
The supplied follow-up review marks command execution as independently confirmed by its author. The implementation review used source inspection and patched literal-value checks, without rerunning that exploit. The relevant activation source is identical between release 21.14.8 and upstream/main 233359cb. The maintainer previously confirmed validation of the reported findings on 21.14.8. The first affected version has not been established. Fixed in 21.14.9.
Known mitigation
Use trusted prompt and destination values. On older releases, disable the environment prompt with VIRTUAL_ENV_DISABLE_PROMPT=1. Recreate environments with virtualenv 21.14.9 or later.
Affected release
- [x] The problem reproduces on virtualenv 21.14.8.
Credits
The original report was supplied by Anthropic's OSS Scanner as ANT-2026-1MOI2X3T. The subsequent maintainer-provided review identified the remaining activation path.
Questions
- Does creating the environment run the payload?
No. The advisory states that creating the environment runs nothing. The command runs when the user activates it and a shell draws the prompt.
- Is this the same as CVE-2026-113718?
No. That one is about the xonsh activation script and legacy encodings such as GBK. This one is about bash, dash and
PS1. Both are fixed in virtualenv 21.14.9.- Can I avoid the issue without upgrading?
Yes, partly. Use only trusted prompt values, or set
VIRTUAL_ENV_DISABLE_PROMPT=1on older releases so the prompt is not changed.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-113713
virtualenv: Temporary app-data can leave dangling seed package links
medium4.4Oct 23, 2026CVE-2026-113714
virtualenv: Downloaded wheel selection and caching precede verification
low2.3Oct 23, 2026CVE-2026-113715
virtualenv: Venv configuration readback can reinterpret path boundaries
low2.0Oct 23, 2026CVE-2026-113717
virtualenv: Pip seeding with download omits wheel digest verification
low2.3Oct 23, 2026CVE-2026-113718
virtualenv: Xonsh activation literals depend on the script decoding codec
high7.1Oct 23, 2026CVE-2026-113719
virtualenv: Seed replacement does not contain metadata deletion paths
medium4.5Oct 23, 2026
