CVE-2026-102938: virtualenv writes prompt values into pyvenv.cfg without sanitizing line boundaries, allowing configuration injection
Summary pyvenv.cfg is a line-based format with no escape syntax. PyEnvCfg.write() wrote values verbatim, while PyEnvCfg.readvalues() parses the file with str.splitlines(). A value containing a line boundary therefore became additional configuration lines, and because reading is last-wins, the injected keys replaced any key written earlier in the file.
Published Sep 30, 2026
Affected packages
virtualenv
- Ecosystem
- PyPI
- Affected
- <= 21.7.10
- Fixed in
- 21.7.11
- Check
pip show virtualenv
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
pyvenv.cfg is a line-based format with no escape syntax. PyEnvCfg.write() wrote values verbatim, while PyEnvCfg._read_values() parses the file with str.splitlines(). A value containing a line boundary therefore became additional configuration lines, and because reading is last-wins, the injected keys replaced any key written earlier in the file.
Impact
The prompt value is the reachable input: it is set by --prompt, by the VIRTUALENV_PROMPT environment variable, or from the config file, and write() emits prompt before home. A crafted prompt can therefore set home in the generated pyvenv.cfg:
$ virtualenv --prompt $'x"\nhome = /attacker/path\nprompt = "z' venv
$ grep '^home' venv/pyvenv.cfg
home = /attacker/pathhome is what tooling reads to locate the base interpreter, so a consumer that trusts it can be pointed elsewhere. implementation, version_info, version, executable, command and virtualenv are also written before prompt and can be replaced the same way.
This requires the prompt to come from somewhere other than the person running the command, for example a CI job templating a branch name into it, tooling deriving an environment name from user-supplied data, or an inherited VIRTUALENV_PROMPT. Where the operator supplies the prompt directly they already control the command line, and the effect is corruption rather than privilege gain: the value is truncated at the boundary and read back with a dangling quote.
Details
The boundary set is the one str.splitlines() recognizes, which is wider than \n: \r, \v, \f, the file, group and record separators, U+0085, U+2028 and U+2029 were all written through unchanged and all split the line when read back.
Patches
PyEnvCfg.write() now collapses those boundaries to spaces as it serializes each line, so it cannot emit a structurally invalid file regardless of what a caller places in content.
Workarounds
Do not pass externally influenced data as the virtualenv prompt. Strip line boundaries from any value before using it as --prompt or VIRTUALENV_PROMPT.
Credited to gaborbernat.
References
- https://github.com/pypa/virtualenv/security/advisories/GHSA-9h9j-4vrj-gf7g
- https://nvd.nist.gov/vuln/detail/CVE-2026-102938
- https://github.com/pypa/virtualenv/pull/3247
- https://github.com/pypa/virtualenv/commit/a30f995461043acb6cacbf3a890951563ccf7140
- https://github.com/pypa/advisory-database/tree/main/vulns/virtualenv/PYSEC-2026-4012.yaml
- https://github.com/pypa/virtualenv/releases/tag/21.7.11
- https://pypi.org/project/virtualenv
- https://github.com/advisories/GHSA-9h9j-4vrj-gf7g
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. No analysis has been written for this entry yet. 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
